archiveorg.wayback.check_availability
Check whether a URL has an archived snapshot in the Wayback Machine, optionally closest to a given timestamp. Returns availability, the archived snapshot URL, and its capture timestamp (Internet Archive Wayback Availability API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/archiveorg.wayback.check-availability.md
What archiveorg.wayback.check_availability does on Apibase
AI agents call archiveorg.wayback.check_availability to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The live URL to check for an archived snapshot in the Wayback Machine (e.g. "example.com" or "https://example.com/page") |
timestamp | string | — | Find the snapshot closest to this timestamp, format YYYYMMDDhhmmss (e.g. "20260101" for Jan 1 2026). Omit for the most recent snapshot |
Parameters from the server's own tool schema.
Why archiveorg.wayback.check_availability is rated Low
Queries Internet Archive API for archived webpage data; no side effects or modifications.
From the tool's definition Check whether a URL has an archived snapshot, returns availability and snapshot URL
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs archiveorg.wayback.check_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archiveorg.wayback.check_availability, this is the rule to start with:
archiveorg.wayback.check_availability is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every archiveorg.wayback.check_availability call is checked against it from then on.
Questions about archiveorg.wayback.check_availability
Check whether a URL has an archived snapshot in the Wayback Machine, optionally closest to a given timestamp. Returns availability, the archived snapshot URL, and its capture timestamp (Internet Archive Wayback Availability API). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
archiveorg.wayback.check_availability accepts 2 parameters: url, timestamp. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for archiveorg.wayback.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 Apibase. Nothing to install.
archiveorg.wayback.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 archiveorg.wayback.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 archiveorg.wayback.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.
archiveorg.wayback.check_availability is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue