query_timeline
AI agents call query_timeline to retrieve information from MemoryMesh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A timeline query on a local memory indexing system is a read-only operation that retrieves temporal event data. No side effects are indicated; the tool neither modifies, deletes, nor executes external actions. The low severity reflects that querying local indexed data poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'query_timeline' indicates a retrieval/querying operation. Server description emphasizes 'semantic search' and 'query your data.' Sibling tools include 'ask_memory' and 'get_document' which are clearly Read operations.
Attacks that exploit this kind of access
query_timeline. It is categorised as a Read tool in the MemoryMesh MCP Server, which means it retrieves data without modifying state.
Register the MemoryMesh MCP server in PolicyLayer and add a rule for query_timeline: 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 MemoryMesh. Nothing to install.
query_timeline 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 query_timeline 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 query_timeline. 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.
query_timeline is provided by the MemoryMesh MCP server (kilhubprojects/memory-mesh). 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 →