AI agents call debugInfo to retrieve information from Heptabase MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Debug information tools typically query and return diagnostic data without modifying system state. The 'debug' prefix conventionally indicates read-only introspection. While the empty description reduces confidence, the broader tool ecosystem and the non-destructive pattern suggest this retrieves information rather than executing arbitrary operations or modifying data.
From the tool's definition Tool name 'debugInfo' suggests information retrieval for diagnostic purposes. Empty description limits certainty.
Documented attack patterns abuse exactly the kind of access debugInfo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Heptabase MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for debugInfo:
{
"version": "1",
"default": "deny",
"tools": {
"debugInfo": {}
}
}debugInfo 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.
debugInfo. It is categorised as a Read tool in the Heptabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Heptabase MCP server in PolicyLayer and add a rule for debugInfo: 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 Heptabase MCP. Nothing to install.
debugInfo 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 debugInfo 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 debugInfo. 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.
debugInfo is provided by the Heptabase MCP server (larrystanley/heptabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Heptabase MCP, 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.
14 Heptabase MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.