Search for a cryptocurrency project's whitepaper PDF using DuckDuckGo.
AI agents call search_whitepaper to retrieve information from Crypto Whitepapers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (whitepaper documents) without creating side effects, modifying data, executing code, or triggering external state changes. It is a read-only search operation. The low severity reflects that misuse would only expose public whitepaper information already accessible via web search, with no destructive or operational impact.
From the tool's definition Tool performs a search operation using DuckDuckGo to retrieve cryptocurrency whitepapers. The description explicitly states it 'Search for a cryptocurrency project's whitepaper PDF' - a retrieval action with no modification, deletion, or execution of external…
Documented attack patterns abuse exactly the kind of access search_whitepaper gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Whitepapers, and nothing reaches the server without passing your rules. This is the rule we recommend for search_whitepaper:
{
"version": "1",
"default": "deny",
"tools": {
"search_whitepaper": {}
}
}search_whitepaper is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for a cryptocurrency project's whitepaper PDF using DuckDuckGo. It is categorised as a Read tool in the Crypto Whitepapers MCP Server, which means it retrieves data without modifying state.
Register the Crypto Whitepapers MCP server in PolicyLayer and add a rule for search_whitepaper: 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 Crypto Whitepapers. Nothing to install.
search_whitepaper 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 search_whitepaper 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 search_whitepaper. 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.
search_whitepaper is provided by the Crypto Whitepapers MCP server (kukapay/crypto-whitepapers-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Whitepapers, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Crypto Whitepapers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.