AI agents call contextual_recall to retrieve information from Tages without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/search operation that retrieves stored context data without side effects. It reads from the SQLite memory store to provide context-aware information to the agent. No data is created, modified, deleted, or executed—only retrieved based on filtering criteria. This is a straightforward Read category tool with minimal risk if invoked on arbitrary arguments, as it simply returns filtered memory records.
From the tool's definition Tool searches and retrieves stored memories filtered by execution context, current files, agent name, or phase. The description uses 'search' and 'retrieval' language with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search memories filtered by execution context — current files, agent name, or phase. More precise than recall for context-aware retrieval. It is categorised as a Read tool in the Tages MCP Server, which means it retrieves data without modifying state.
Register the Tages MCP server in PolicyLayer and add a rule for contextual_recall: 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 Tages. Nothing to install.
contextual_recall 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 contextual_recall 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 contextual_recall. 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.
contextual_recall is provided by the Tages MCP server (ryantlee25-droid/tages). 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 →