memory_addDocument · Chain Debugger MCP Server MCP

WHAT IT DOES

What memory_addDocument does on Chain Debugger MCP Server

AI agents use memory_addDocument to create or update resources in Chain Debugger MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chain Debugger MCP Server environment.

WHY IT NEEDS A POLICY

Why memory_addDocument needs a policy

The tool performs a Write action—it creates or adds data to a memory store. While the description is empty (reducing confidence slightly), the name and server context (blockchain monitoring with state management) suggest it stores reversible data. It is not Destructive (no deletion), Execute (no code execution), Financial (no money movement), or Read (it modifies, not just retrieves).

From the tool's definition Tool name 'memory_addDocument' indicates creation/modification of document data. Server context shows this is a blockchain debugging tool with transaction simulation and monitoring; adding documents to memory likely stores configuration, query templates, or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_addDocument Rate-limited

memory_addDocument stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_addDocument": {
      "limits": [
        {
          "counter": "memory_adddocument_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chain Debugger MCP Server, so you can run agents against it safely.

FAQ

Questions about memory_addDocument

What does the memory_addDocument tool do? +

memory_addDocument. It is categorised as a Write tool in the Chain Debugger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_addDocument? +

Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for memory_addDocument: 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.

What risk level is memory_addDocument? +

memory_addDocument is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_addDocument? +

Yes. Add a rate_limit block to the memory_addDocument 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.

How do I block memory_addDocument completely? +

Set action: deny in the PolicyLayer policy for memory_addDocument. 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.

What MCP server provides memory_addDocument? +

memory_addDocument 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.