Search past debugging sessions.
AI agents call debug_history to retrieve information from M3 Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical debugging data. The verb 'search' and the passive retrieval nature indicate a read-only operation that queries existing information without side effects. No data is created, modified, or deleted. Severity is low because the blast radius of an AI agent searching debug history is minimal—it may access internal debugging logs but cannot alter system state.
From the tool's definition Tool name is 'debug_history' and description states 'Search past debugging sessions' — a query/retrieval operation with no modification or destructive capability.
Documented attack patterns abuse exactly the kind of access debug_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M3 Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_history:
{
"version": "1",
"default": "deny",
"tools": {
"debug_history": {}
}
}debug_history 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.
Search past debugging sessions. It is categorised as a Read tool in the M3 Memory MCP Server, which means it retrieves data without modifying state.
Register the M3 Memory MCP server in PolicyLayer and add a rule for debug_history: 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 M3 Memory. Nothing to install.
debug_history 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_history 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_history. 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_history is provided by the M3 Memory MCP server (skynetcmd/m3-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from M3 Memory, 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.
43 M3 Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.