search
Search the web and return clean results in JSON, Markdown, or HTML
This record as markdown: /tools/com-geekflare-mcp/search.md
What search does on Mcp
AI agents call search to retrieve information from Mcp 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 |
|---|---|---|---|
time | string | — | Time filter: any, d, w, m, y, d7, h6 etc. |
limit | number | — | Number of results |
query | string | Yes | Search query |
format | string | — | |
scrape | boolean | — | Scrape content from result URLs |
source | string | — | |
category | string | — | |
location | string | — | Country code (ISO alpha-2) |
scrapeLimit | number | — | Number of URLs to scrape |
excludeDomains | array | — | Exclude these domains |
groundedAnswer | boolean | — | Generate AI-grounded answer from results |
includeDomains | array | — | Only include these domains |
Parameters from the server's own tool schema.
Why search is rated Low
This tool retrieves and queries web search results without creating, modifying, deleting, or executing code. It has no side effects on external systems beyond issuing search queries. The blast radius of misuse is minimal—an agent could perform excessive searches or access sensitive information already public on the web, but cannot damage systems or resources.
From the tool's definition Tool description states 'Search the web and return clean results' with output formats (JSON, Markdown, HTML). The name 'search' and description indicate data retrieval with no modification or deletion of data.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search, this is the rule to start with:
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 Mcp, apply this rule, and every search call is checked against it from then on.
Questions about search
Search the web and return clean results in JSON, Markdown, or HTML. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
search accepts 12 parameters: time, limit, query, format, scrape, source, category, location, scrapeLimit, excludeDomains, groundedAnswer, includeDomains. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for 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 Mcp. Nothing to install.
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 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 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.
search is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue