store
AI agents use store to create or update resources in Agent Memory Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Memory Bridge environment.
The 'store' tool creates or modifies memory records for a coding agent, which is a reversible Write operation. While the description is empty, the name combined with server purpose (storing agent memory/decisions) and sibling functions (recall, forget, promote) clearly indicate data creation/modification.
From the tool's definition Tool name 'store' and context of 'Agent Memory Bridge' that 'turns real sessions into reusable decisions, gotchas, and domain knowledge' indicates persistent storage of data.
Attacks that exploit this kind of access
store. It is categorised as a Write tool in the Agent Memory Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Memory Bridge MCP server in PolicyLayer and add a rule for store: 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 Agent Memory Bridge. Nothing to install.
store 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 store 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 store. 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.
store is provided by the Agent Memory Bridge MCP server (zzhang82/agent-memory-bridge). 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 →