archive_search
Search the Internet Archive (archive.org) for items.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/archive-search.md
What archive_search does on UnClick
AI agents call archive_search to retrieve information from UnClick 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 | number | — | Page number (default 1) |
limit | number | — | Results per page (max 20, default 10) |
query | string | Yes | Search query |
mediatype | string | — | Filter: texts, audio, movies, software, image, collection |
Parameters from the server's own tool schema.
Why archive_search is rated Low
This tool performs a read-only search query against the Internet Archive. It retrieves/queries data with no side effects, write operations, or destructive capabilities. Misuse potential is minimal as it only reads publicly available archived data.
From the tool's definition Search the Internet Archive (archive.org) for items
Attacks that exploit this kind of access
The rule that runs archive_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_search, this is the rule to start with:
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 UnClick, apply this rule, and every archive_search call is checked against it from then on.
Questions about archive_search
Search the Internet Archive (archive.org) for items. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
archive_search accepts 4 parameters: page, limit, query, mediatype. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for 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 UnClick. Nothing to install.
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 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 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.
archive_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue