archiveorg.archive.search
Search 40M+ items in the Internet Archive — books, movies, audio, software, images, and archived web pages. Filter by mediatype (texts/movies/audio/software/image/data/web) and creator. Returns identifier, title, creator, date, and description for each match (Internet Archive advancedsearch.php)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/archiveorg.archive.search.md
What archiveorg.archive.search does on Apibase
AI agents call archiveorg.archive.search 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default: 1) |
rows | integer | — | Number of results to return (default: 10, max: 50) |
query | string | — | Full-text search query across title, description, and text (e.g. "moon landing 1969"). Omit to browse by mediatype/creator alone |
creator | string | — | Filter by creator/author/uploader name (e.g. "NASA", "mark twain") |
mediatype | string | — | Filter by item type: texts (books/docs), movies, audio, software, image, data, web (archived sites), collection |
Parameters from the server's own tool schema.
Why archiveorg.archive.search is rated Low
Tool queries archived data without modifying, deleting, or executing operations.
From the tool's definition Search 40M+ items in the Internet Archive
Attacks that exploit this kind of access
The rule that runs archiveorg.archive.search 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.archive.search, this is the rule to start with:
archiveorg.archive.search 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.archive.search call is checked against it from then on.
Questions about archiveorg.archive.search
Search 40M+ items in the Internet Archive — books, movies, audio, software, images, and archived web pages. Filter by mediatype (texts/movies/audio/software/image/data/web) and creator. Returns identifier, title, creator, date, and description for each match (Internet Archive advancedsearch.php). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
archiveorg.archive.search accepts 5 parameters: page, rows, query, creator, mediatype. 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.archive.search: 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.archive.search 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.archive.search 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.archive.search. 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.archive.search 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