pin_memory
AI agents use pin_memory to create or update resources in Mem0 Mcp Toggle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mem0 Mcp Toggle environment.
Pinning a memory modifies stored data (marking it as pinned/prioritized) but does not delete, destroy, or create new memories. This is a reversible Write operation. Confidence is moderate (0.6) due to the missing description; if pinning triggers irreversible side effects or cascading deletions, it could be Destructive, but the name and context suggest a simple metadata update.
From the tool's definition Tool name 'pin_memory' suggests modifying memory state or metadata by marking a memory as pinned/favorited. Sibling tools include 'add_memories', 'add_memory', 'delete_memory', 'set_confidence', 'set_memory_type', 'set_provenance'—all Write operations.
Attacks that exploit this kind of access
pin_memory. It is categorised as a Write tool in the Mem0 Mcp Toggle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mem0 Mcp Toggle MCP server in PolicyLayer and add a rule for pin_memory: 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 Mem0 Mcp Toggle. Nothing to install.
pin_memory 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 pin_memory 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 pin_memory. 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.
pin_memory is provided by the Mem0 Mcp Toggle MCP server (ost527/mem0-mcp-toggle). 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 →