Debug the communication directories and show their status
AI agents call debug_directories to retrieve information from SP-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays diagnostic information about communication directories without modifying, executing operations on external systems, or causing side effects. It is purely informational—typical of debugging/monitoring utilities that read internal state for troubleshooting purposes.
From the tool's definition Tool name 'debug_directories' and description 'show their status' indicate a diagnostic query operation. 'Debug' and 'show' are read-only inspection actions.
Documented attack patterns abuse exactly the kind of access debug_directories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SP-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_directories:
{
"version": "1",
"default": "deny",
"tools": {
"debug_directories": {}
}
}debug_directories 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 the communication directories and show their status. It is categorised as a Read tool in the SP-MCP MCP Server, which means it retrieves data without modifying state.
Register the SP- MCP server in PolicyLayer and add a rule for debug_directories: 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 SP-MCP. Nothing to install.
debug_directories 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_directories 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_directories. 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_directories is provided by the SP- MCP server (organicmoron/sp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 SP-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 SP-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.