query_at
AI agents call query_at 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.
Based on the server's stated purpose of retrieving historical information and the name pattern 'query_at' (a retrieval operation), this tool almost certainly retrieves data from the knowledge graph at a specific time without modifying or deleting anything. The blast radius of misuse is low—incorrect queries return wrong data but cause no side effects or damage.
From the tool's definition Tool name 'query_at' suggests a temporal query operation (likely 'at' indicates a point in time), consistent with the server's 'time-travel queries' capability mentioned in the server description. The sibling tool 'get_memory' is explicitly a Read operation.
Attacks that exploit this kind of access
query_at. 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 query_at: 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.
query_at 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_at 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_at. 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_at 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 →