Record an important technical decision
AI agents use add_decision to create or update resources in MCP Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memory Server environment.
This tool creates new entries (decisions) in a persistent memory system. It is Write rather than Read (it stores, not retrieves), not Destructive (decisions can be modified or removed), not Execute (it doesn't run code or trigger external operations), and not Financial.
From the tool's definition Tool name 'add_decision' and description 'Record an important technical decision' indicates creation of new decision records in persistent memory.
Attacks that exploit this kind of access
Record an important technical decision. It is categorised as a Write tool in the MCP Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for add_decision: 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 MCP Memory Server. Nothing to install.
add_decision 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 add_decision 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 add_decision. 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.
add_decision is provided by the MCP Memory Server MCP server (keleshteri/mcp-memory). 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 →