AI agents call get_memory to retrieve information from Jamot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries stored memory data using filters (key or tag), which is a read-only operation. It has no capacity to modify, delete, or execute external operations. The only risk is potential exposure of sensitive team context or task information if an agent has unauthorized access, but the tool itself performs no irreversible actions and carries low blast radius.
From the tool's definition Tool name 'get_memory' and description 'Retrieve past memories. Filter by key (partial match) or tag' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve past memories. Filter by key (partial match) or tag. It is categorised as a Read tool in the Jamot MCP MCP Server, which means it retrieves data without modifying state.
Register the Jamot MCP server in PolicyLayer and add a rule for get_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 Jamot MCP. Nothing to install.
get_memory 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 get_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 get_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.
get_memory is provided by the Jamot MCP server (jamot-pro/jamot-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 →