Check if a URL has been archived
AI agents call check_archive_status to retrieve information from MCP Wayback Machine Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the Wayback Machine to determine whether a URL exists in the archive. It does not create, modify, delete, or execute any operations. It has no side effects and presents minimal risk even if misused by an AI agent, as it merely gathers information about the existence of archived pages.
From the tool's definition Tool description: 'Check if a URL has been archived' — a pure query operation that retrieves archive metadata without modification. The server description confirms this involves 'check archive statistics' as a read-only capability.
Attacks that exploit this kind of access
Check if a URL has been archived. It is categorised as a Read tool in the MCP Wayback Machine Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Wayback Machine Server MCP server in PolicyLayer and add a rule for check_archive_status: 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 MCP Wayback Machine Server. Nothing to install.
check_archive_status 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_archive_status 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_archive_status. 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_archive_status is provided by the MCP Wayback Machine Server MCP server (pl974/mcp-wayback-machine). 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 →