Get one memory store's details by memstore_* id (name, description, timestamps).
AI agents call memory_store_get to retrieve information from Managed Agent Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about a memory store without creating, modifying, deleting, or executing any operations. It has a minimal blast radius as it only exposes stored metadata. The low severity reflects that exposure of memory store metadata poses minimal security risk compared to other categories.
From the tool's definition Tool retrieves memory store details by ID, returning name, description, and timestamps with no modification or side effects. The verb 'get' and the action of fetching metadata indicates a read-only operation.
Attacks that exploit this kind of access
Get one memory store's details by memstore_* id (name, description, timestamps). It is categorised as a Read tool in the Managed Agent Control MCP Server, which means it retrieves data without modifying state.
Register the Managed Agent Control MCP server in PolicyLayer and add a rule for memory_store_get: 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 Managed Agent Control. Nothing to install.
memory_store_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_store_get 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 memory_store_get. 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.
memory_store_get is provided by the Managed Agent Control MCP server (modus-agendi/managed-agent-control-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 →