Decision memory add (user_id based)
AI agents use decision_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.
This tool creates or modifies data (a decision memory entry) in a reversible manner. The 'add' operation is characteristic of Write category tools. Severity is medium because modifying user-specific memory could affect application behavior and decision-making, but the effect is typically reversible (entries can be removed or updated).
From the tool's definition Tool name contains 'add' and description explicitly states 'add' operation. The 'user_id based' qualifier indicates it modifies user-specific data structures.
Attacks that exploit this kind of access
Decision 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.
Register the Universal Dev MCP server in PolicyLayer and add a rule for decision_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.
decision_memory_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the decision_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.
Set action: deny in the PolicyLayer policy for decision_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.
decision_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.
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 →