check_url_updates

Check all URL-sourced documents for updates by comparing Last-Modified headers. Detects when source URLs have been modified since last scrape.

Server TDZ C64 Knowledge michaeltroelsen/tdz-c64-knowledge
Category Read
Risk class Low
Parameters 00 required

What check_url_updates does on TDZ C64 Knowledge

AI agents call check_url_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.

Why check_url_updates needs a policy

The tool retrieves HTTP metadata (Last-Modified headers) to determine if source documents have been updated since last ingestion. This is a read-only information retrieval operation with no side effects. Even though it scans multiple documents, it only queries their HTTP properties and reports findings. The worst-case misuse would be discovering outdated knowledge base content, which is low-impact.

From the tool's definition The tool performs a passive check by comparing Last-Modified headers from URL sources. It detects changes ("comparing Last-Modified headers", "when source URLs have been modified") without modifying, executing code, deleting data, or moving money.

Questions about check_url_updates

What does the check_url_updates tool do? +

Check all URL-sourced documents for updates by comparing Last-Modified headers. Detects when source URLs have been modified since last scrape. It is categorised as a Read tool in the TDZ C64 Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_url_updates? +

Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for check_url_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.

What risk level is check_url_updates? +

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

Can I rate-limit check_url_updates? +

Yes. Add a rate_limit block to the check_url_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.

How do I block check_url_updates completely? +

Set action: deny in the PolicyLayer policy for check_url_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.

What MCP server provides check_url_updates? +

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

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