search_sites
Full-text search across the authenticated account's sites (names, metadata, and text content).
This record as markdown: /tools/ai-dataecho-mcp/search-sites.md
What search_sites does on Mcp
AI agents call search_sites 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 |
|---|---|---|---|
limit | number | — | Max results (optional) |
query | string | Yes | Search query |
Parameters from the server's own tool schema.
Why search_sites is rated Low
This tool retrieves and queries information (site names, metadata, text content) without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal — an agent could exfiltrate information about existing sites but cannot deploy, delete, or alter them. This is a pure Read operation.
From the tool's definition Tool performs 'Full-text search across the authenticated account's sites (names, metadata, and text content)' — a query operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs search_sites 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_sites, this is the rule to start with:
search_sites 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_sites call is checked against it from then on.
Questions about search_sites
Full-text search across the authenticated account's sites (names, metadata, and text content). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
search_sites accepts 2 parameters: limit, query. 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_sites: 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_sites 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_sites 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_sites. 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_sites is provided by the MCP server (https://dataecho.ai/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