AI agents call explain_code to retrieve information from Sfgraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and partial description, 'explain_code' appears to be a query/analysis tool that retrieves and explains existing code from the Salesforce knowledge graph. It does not create, modify, delete, execute commands, or commit financial transactions. The tool operates on a local SQLite + vector index with read-only semantics for code comprehension and reasoning.
From the tool's definition Tool name is 'explain_code' and description indicates it is used to explain code. The incomplete description ('USE THIS for any') suggests this tool retrieves or analyzes code without modifying it.
Attacks that exploit this kind of access
USE THIS for any. It is categorised as a Read tool in the Sfgraph MCP Server, which means it retrieves data without modifying state.
Register the Sfgraph MCP server in PolicyLayer and add a rule for explain_code: 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 Sfgraph. Nothing to install.
explain_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the explain_code 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 explain_code. 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.
explain_code is provided by the Sfgraph MCP server (ryanstark24/sfgraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →