search_public_apis
Searches a curated catalog of 600+ free public APIs (no key, HTTPS) for embedding live data in display HTML via fetch(): weather, news, finance, sports, images, food and 40+ more categories. Use when generating HTML that needs live internet data. Set list_categories=true to get the category menu ...
This record as markdown: /tools/de-agentview-agentview-mcp/search-public-apis.md
What search_public_apis does on agentView
AI agents call search_public_apis to retrieve information from agentView 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 |
|---|---|---|---|
limit | integer | — | Maximum results, 1-20. Default 10. |
query | string | — | Free-text search, e.g. 'weather forecast', 'bitcoin price', 'jokes'. |
category | string | — | Category ID filter, e.g. 'weather', 'finance', 'news'. Omit for all. |
cors_only | boolean | — | true returns only APIs with confirmed browser CORS support. Default false. |
list_categories | boolean | — | true returns all categories with API counts instead of search results. |
Parameters from the server's own tool schema.
Why search_public_apis is rated Low
Even though search_public_apis only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_public_apis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_public_apis, this is the rule to start with:
search_public_apis 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 agentView, apply this rule, and every search_public_apis call is checked against it from then on.
Questions about search_public_apis
Searches a curated catalog of 600+ free public APIs (no key, HTTPS) for embedding live data in display HTML via fetch(): weather, news, finance, sports, images, food and 40+ more categories. Use when generating HTML that needs live internet data. Set list_categories=true to get the category menu with counts instead of search results. Returns docs links, CORS status and fetch() hints. No authentication required. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
search_public_apis accepts 5 parameters: limit, query, category, cors_only, list_categories. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for search_public_apis: 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 agentView. Nothing to install.
search_public_apis 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_public_apis 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_public_apis. 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_public_apis is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue