memory_getDocument
AI agents call memory_getDocument to retrieve information from Chain Debugger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention 'get' + 'Document' implies querying or retrieving stored data without side effects. In the context of a debugging server, this likely retrieves previously stored analysis or context data. No evidence suggests the tool modifies state, executes code, deletes data, or performs financial operations. Classification is Read despite missing description details.
From the tool's definition Tool name 'memory_getDocument' indicates a retrieval operation. The 'get' prefix strongly suggests reading or fetching data from memory storage, with no indication of modification, deletion, or execution. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
memory_getDocument. It is categorised as a Read tool in the Chain Debugger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for memory_getDocument: 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 Chain Debugger MCP Server. Nothing to install.
memory_getDocument 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 memory_getDocument 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 memory_getDocument. 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.
memory_getDocument is provided by the Chain Debugger MCP Server MCP server (optimusopus/chain-debugger-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →