AI agents call check_availability to retrieve information from Wayback without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the Wayback Machine's archived snapshots database to determine availability and retrieve metadata about the closest matching snapshot. It performs a lookup operation with no side effects, no data modification, and no external command execution. The blast radius of misuse is minimal—an agent could only retrieve publicly archived web snapshots, which is read-only access to historical web data.
From the tool's definition Tool description states 'Check if a URL has been archived' and 'return the closest snapshot' — purely informational retrieval from the Internet Archive. No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
Check if a URL has been archived by the Wayback Machine and return the closest snapshot. It is categorised as a Read tool in the Wayback MCP Server, which means it retrieves data without modifying state.
Register the Wayback MCP server in PolicyLayer and add a rule for check_availability: 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 Wayback. Nothing to install.
check_availability 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_availability 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_availability. 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_availability is provided by the Wayback MCP server (lakshyamehta03/wayback-machine-mcp). 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 →