query_at

query_at

Server Chronos MCP synaptikal/chronosmcp
Category Read
Risk class Low
Parameters 00 required

What query_at does on Chronos MCP

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.

Why query_at needs a policy

The tool appears designed to retrieve historical data from the knowledge graph at specified time points. Even though the description is missing, the naming convention 'query_at' combined with the server's stated purpose of time-travel queries and the pattern of read-only sibling tools strongly suggests a retrieval operation with no side effects.

From the tool's definition Tool name 'query_at' suggests querying data at a specific point in time, consistent with the server's capability for 'time-travel queries to reconstruct past information'.

Questions about query_at

What does the query_at tool do? +

query_at. It is categorised as a Read tool in the Chronos MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_at? +

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.

What risk level is query_at? +

query_at is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_at? +

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.

How do I block query_at completely? +

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.

What MCP server provides query_at? +

query_at 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.