debug_memory_add · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What debug_memory_add does on Universal Dev MCP

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

WHY IT NEEDS A POLICY

Why debug_memory_add needs a policy

This tool creates or appends to debug memory entries, which is a reversible modification of data. It does not delete, execute arbitrary code, or cause irreversible changes, so Write is the appropriate category. Severity is medium because misuse could pollute debug logs or create unwanted memory records affecting system behavior, but the impact is limited to debugging artifacts and user-scoped data.

From the tool's definition Tool name contains 'add' and description states 'Debug memory add', indicating creation or modification of memory records associated with a user_id. The description is minimal but 'add' clearly signals a Write operation that creates new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_memory_add Rate-limited

debug_memory_add 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": {
    "debug_memory_add": {
      "limits": [
        {
          "counter": "debug_memory_add_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 Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about debug_memory_add

What does the debug_memory_add tool do? +

Debug memory add (user_id based). It is categorised as a Write tool in the Universal Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debug_memory_add? +

Register the Universal Dev MCP server in PolicyLayer and add a rule for debug_memory_add: 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 Universal Dev MCP. Nothing to install.

What risk level is debug_memory_add? +

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

Can I rate-limit debug_memory_add? +

Yes. Add a rate_limit block to the debug_memory_add 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 debug_memory_add completely? +

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

debug_memory_add is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.