Check all indexed documents for updates. Detects files that have been modified since indexing and optionally re-indexes them automatically.
AI agents call check_updates 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 performs a read-like operation: scanning indexed documents, comparing their modification timestamps, and reporting changes. While re-indexing may occur, it is reversible (documents can be re-indexed again), and the tool does not delete, create new data permanently, or execute external code based on user input.
From the tool's definition Tool name 'check_updates' and description 'Check all indexed documents for updates. Detects files that have been modified since indexing' indicate a query/monitoring operation.
Attacks that exploit this kind of access
Check all indexed documents for updates. Detects files that have been modified since indexing and optionally re-indexes them automatically. 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 check_updates: 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.
check_updates 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 check_updates 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 check_updates. 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.
check_updates 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 →