Retrieve lists of files, metadata, summaries, or specific message ranges. Options for view_type: 'content', 'metadata', 'summary'.
AI agents call get_chat_logs to retrieve information from Chronicle MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical chat log data without creating, modifying, deleting, or executing operations. It is a straightforward query/fetch operation against stored conversation history. The local-first design and use case (memory vault) further confirm this is for accessing historical data. No side effects or state changes occur from retrieval alone.
From the tool's definition Tool description states it 'Retrieve[s] lists of files, metadata, summaries, or specific message ranges' with view_type options for 'content', 'metadata', 'summary'.
Attacks that exploit this kind of access
Retrieve lists of files, metadata, summaries, or specific message ranges. Options for view_type: 'content', 'metadata', 'summary'. It is categorised as a Read tool in the Chronicle MCP MCP Server, which means it retrieves data without modifying state.
Register the Chronicle MCP server in PolicyLayer and add a rule for get_chat_logs: 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 Chronicle MCP. Nothing to install.
get_chat_logs 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 get_chat_logs 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 get_chat_logs. 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.
get_chat_logs is provided by the Chronicle MCP server (pypi:chronicle-mcp-server). 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 →