Debug tool to verify which version of the code is running.
AI agents call debug_code_path to retrieve information from Scopecraft Command without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to only read/inspect code version information for debugging purposes, with no side effects. However, the description is vague and doesn't fully detail what 'debug' entails. Confidence is moderate because 'debug' could imply execution of diagnostic routines, but the stated purpose is merely verification/inspection of the running code version.
From the tool's definition "Debug tool to verify which version of the code is running"
Documented attack patterns abuse exactly the kind of access debug_code_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scopecraft Command, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_code_path:
{
"version": "1",
"default": "deny",
"tools": {
"debug_code_path": {}
}
}debug_code_path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Debug tool to verify which version of the code is running. It is categorised as a Read tool in the Scopecraft Command MCP Server, which means it retrieves data without modifying state.
Register the Scopecraft Command MCP server in PolicyLayer and add a rule for debug_code_path: 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 Scopecraft Command. Nothing to install.
debug_code_path 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 debug_code_path 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 debug_code_path. 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.
debug_code_path is provided by the Scopecraft Command MCP server (scopecraft/command). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Scopecraft Command tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Scopecraft Command tools catalogued and risk-classified — across an index of 42,500+ MCP servers.