Get historical context for a specific year. Returns events from the target year plus surrounding years to provide temporal context.
AI agents call get_historical_context to retrieve information from TDZ C64 Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical context information about specific years. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal: an AI agent cannot cause harm by requesting historical event data. It aligns with the Read category (retrieves or queries data; no side effects).
From the tool's definition The tool description states it "Returns events from the target year plus surrounding years" — a pure retrieval operation with no modification, deletion, or side effects. The verb "Get" and "Returns" indicate read-only data access.
Attacks that exploit this kind of access
Get historical context for a specific year. Returns events from the target year plus surrounding years to provide temporal context. It is categorised as a Read tool in the TDZ C64 Knowledge MCP Server, which means it retrieves data without modifying state.
Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for get_historical_context: 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 TDZ C64 Knowledge. Nothing to install.
get_historical_context 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_historical_context 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_historical_context. 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_historical_context is provided by the TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). 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 →