Skip to content

SF Guardrail ​

Salesforce-aware safety hooks — file protection policies, dangerous-command gating, org-aware confirmation, and native high-value mutation mediation

What it does ​

Salesforce-aware safety layer for pi: file-protection policies, AST-matched command gating, authenticated-fact and trusted-URL org classification, org-aware confirmation on production deploys/Apex/DML/destructive REST, native high-value mutation mediation, plus a once-per-session prompt-injection that teaches the LLM the gating categories and validate-first workflow.

Start ​

Open the extension from its primary command:

text
/sf-guardrail

Open its Manager detail or change its package state with:

text
/sf-pi open sf-guardrail
/sf-pi enable sf-guardrail
/sf-pi disable sf-guardrail

Safety notes ​

  • Fail-closed in headless mode unless SF_GUARDRAIL_ALLOW_HEADLESS=1.
  • Every block / allow / confirm decision is persisted as an audit entry.
  • Power Tool Mode can persistently auto-approve selected confirm-class decisions; authenticated developer/scratch/sandbox/trial targets and trusted Salesforce-owned non-production URLs honor that setting, while production/unknown org auto-approve is a separate opt-in and hard blocks are never bypassed.
  • Operator auto-approve env mode is process-scoped, audited, and does not bypass hard blocks.
  • Known high-value native tool mutations are mediated before execution through the same Safety Kernel and HITL path, including first-slice Agent Script lifecycle, SF Integrate setup and credential population, SF Flow activation/deactivation, Data 360, Apex, Slack Canvas, SF Browser commit surfaces, Salesforce MCP record writes/deletes, Backup and Recover writes, Content writes, Headless 360 dispatch, DX mutations, hosted Data 360 execution, every experimental Agentforce Sales operation, and managed external MCP operations. Integration and Flow production/unknown restrictions use configurable org-operation rules (Block by default), and both families participate in Power Tool Mode. Legacy SObject and unsupported hosted mutations fail closed.
  • alwaysActive=false but disabling removes the safety layer entirely; the manager surfaces this clearly.

Exact reference ​

Show commands, tools, providers, and hooks
  • Extension id: sf-guardrail
  • Intent: Work safely
  • Category: Safety
  • Maturity: stable
  • Default state: on
  • Commands: /sf-guardrail
  • LLM tools: none
  • Providers: none
  • Events/hooks: session_start, session_tree, before_agent_start, tool_call, context

For contributors ​

Troubleshooting ​

See the Troubleshooting section in the full README for extension-specific recovery steps.

Released under the Apache-2.0 License.