set_provenance
AI agents use set_provenance 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.
The tool likely modifies memory record metadata (provenance = data origin/lineage). With an empty description, confidence is reduced, but the naming pattern and context of a memory management system indicate this is a Write operation that could alter how memories are tracked or attributed. Not Destructive (reversible), not Read (performs modification).
From the tool's definition Tool name 'set_provenance' suggests metadata modification; empty description limits assessment. Sibling tools include write operations (add_memories, delete_memory, pin_memory, set_confidence, set_memory_type) in a memory management system.
Attacks that exploit this kind of access
set_provenance. 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 set_provenance: 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.
set_provenance 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 set_provenance 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 set_provenance. 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.
set_provenance 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 →