Fetch the archived page content. Returns status, headers, and text content.
AI agents call get_archived_page to retrieve information from Wayback Machine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical website content and metadata without side effects. It does not create, modify, delete, or execute any code. The data returned is pre-existing archived content from the Wayback Machine, making this a straightforward read operation with minimal security risk.
From the tool's definition Tool fetches archived page content from the Internet Archive Wayback Machine, returning status, headers, and text content. This is a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Fetch the archived page content. Returns status, headers, and text content. It is categorised as a Read tool in the Wayback Machine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wayback Machine MCP Server MCP server in PolicyLayer and add a rule for get_archived_page: 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 Machine MCP Server. Nothing to install.
get_archived_page 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 get_archived_page 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 get_archived_page. 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.
get_archived_page is provided by the Wayback Machine MCP Server MCP server (sisilet/wayback-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 →