Debug memory list (user_id based)
AI agents call debug_memory_list to retrieve information from Universal Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries debug memory data indexed by user_id. It has no side effects—it only lists or fetches existing information. While debug data could potentially contain sensitive information (lowering confidence slightly), the action itself is a read-only query operation, placing it in the Read category with low severity.
From the tool's definition Tool name 'debug_memory_list' and description 'Debug memory list (user_id based)' indicate retrieval of debug/memory information filtered by user_id. No modification, deletion, or execution of arbitrary code is implied.
Attacks that exploit this kind of access
Debug memory list (user_id based). It is categorised as a Read tool in the Universal Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Universal Dev MCP server in PolicyLayer and add a rule for debug_memory_list: 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.
debug_memory_list 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_memory_list 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_memory_list. 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_memory_list 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.
debug_memory_list is one line of Universal Dev's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →