recall
AI agents call recall to retrieve information from Chronos MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name 'recall' combined with server context strongly indicates a retrieval operation. The server's stated purpose is to 'store notes' and enable queries; 'recall' fits the Read category as it retrieves previously stored information. No evidence suggests mutation, execution, deletion, or financial operations.
From the tool's definition Tool named 'recall' on a memory/knowledge graph MCP server alongside tools like 'query_at', 'query_similar', and 'remember'. The server explicitly provides functionality for 'storing notes' and 'perform time-travel queries to reconstruct past information'.
Attacks that exploit this kind of access
recall. It is categorised as a Read tool in the Chronos MCP MCP Server, which means it retrieves data without modifying state.
Register the Chronos MCP server in PolicyLayer and add a rule for 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 Chronos MCP. Nothing to install.
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 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 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.
recall is provided by the Chronos MCP server (synaptikal/chronosmcp). 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 →