related_memories
AI agents call related_memories 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.
This tool retrieves related memories from the knowledge graph—a read-only query operation with no side effects. The absence of a description lowers confidence slightly, but the name and server context clearly indicate data retrieval. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'related_memories' indicates querying or retrieving memories. The server provides 'a persistent local memory and structured knowledge graph' and mentions 'recall information using keyword relevance' as a core capability.
Attacks that exploit this kind of access
related_memories. 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 related_memories: 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.
related_memories 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 related_memories 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 related_memories. 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.
related_memories is provided by the Chronos MCP server (kodaxadev/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 →