AI agents call wait_for_cdn_freshness to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads/checks CDN state by polling a URL and comparing SHA-256 hashes. It does not modify, delete, or create any data. It simply waits and verifies that a CDN URL is serving expected content. Severity is low as misuse would only result in wasted compute time or false confirmations.
From the tool's definition 'Polls the CDN until a MUTABLE blob URL serves the expected SHA-256, or the timeout elapses' — this is a polling/read operation that checks/verifies content, with no side effects described
Attacks that exploit this kind of access
Polls the CDN until a MUTABLE blob URL serves the expected SHA-256, or the timeout elapses. For mutable URLs only — for immutable URLs (the. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for wait_for_cdn_freshness: 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 Run402. Nothing to install.
wait_for_cdn_freshness 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 wait_for_cdn_freshness 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 wait_for_cdn_freshness. 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.
wait_for_cdn_freshness is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
wait_for_cdn_freshness is one line of Run402's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →