sf_disable_debug_logs
Turns Apex debug logging back off by deleting active TraceFlag records via the Tooling API. The counterpart to sf_enable_debug_logs. username: stop tracing for this user. Omit to disable ALL active trace flags in the org. includeExpired: also clean up already-expired trace flags (off by default —...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-disable-debug-logs.md
What sf_disable_debug_logs does on Salesforce Metadata Mcp
AI agents use sf_disable_debug_logs to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.
Why sf_disable_debug_logs is rated Medium
An AI agent can call sf_disable_debug_logs faster than any human can review: one bad instruction and it creates or modifies resources in Salesforce Metadata Mcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs sf_disable_debug_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_disable_debug_logs, this is the rule to start with:
sf_disable_debug_logs stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_disable_debug_logs call is checked against it from then on.
Questions about sf_disable_debug_logs
Turns Apex debug logging back off by deleting active TraceFlag records via the Tooling API. The counterpart to sf_enable_debug_logs. username: stop tracing for this user. Omit to disable ALL active trace flags in the org. includeExpired: also clean up already-expired trace flags (off by default — expired flags are already inert and sweeping them makes the count look alarming for nothing). Trace flags set by sf_enable_debug_logs expire on their own, so this is for stopping early — typically once you have captured the log you needed, to avoid filling the org. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_disable_debug_logs: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Salesforce Metadata Mcp. Nothing to install.
sf_disable_debug_logs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_disable_debug_logs rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for sf_disable_debug_logs. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
sf_disable_debug_logs is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue