AI agents call debug_info to retrieve information from MCP Reloader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic/debug metadata about the server state. It has no side effects, does not modify data, execute code, or delete anything. It's a straightforward read operation with minimal security risk, though debug information could potentially reveal implementation details if exposed to untrusted parties. Classified as Read/low severity.
From the tool's definition Tool is described as 'Get debug information about the MCP server' - a retrieval operation with no modification, deletion, or execution of external commands. Returns diagnostic information only.
Documented attack patterns abuse exactly the kind of access debug_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Reloader, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_info:
{
"version": "1",
"default": "deny",
"tools": {
"debug_info": {}
}
}debug_info 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.
Get debug information about the MCP server. It is categorised as a Read tool in the MCP Reloader MCP Server, which means it retrieves data without modifying state.
Register the MCP Reloader MCP server in PolicyLayer and add a rule for debug_info: 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 MCP Reloader. Nothing to install.
debug_info 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_info 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_info. 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_info is provided by the MCP Reloader MCP server (mizchi/mcp-reloader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Reloader, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Reloader tools catalogued and risk-classified — across an index of 43,000+ MCP servers.