Natural-language search across the catalog. Use for fuzzy queries like
AI agents call search_by_query to retrieve information from AI List My Business without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a business directory and returns read-only results (business catalog data and booking URLs). It has no side effects—it does not create, modify, delete, execute commands, or move money. The zero PII constraint and booking URL generation are informational only. This is a classic Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool performs 'Natural-language search across the catalog' and 'returns business catalog data and UTM-tagged booking URLs' with explicit note of 'zero PII'.
Attacks that exploit this kind of access
Natural-language search across the catalog. Use for fuzzy queries like. It is categorised as a Read tool in the AI List My Business MCP Server, which means it retrieves data without modifying state.
Register the AI List My Business MCP server in PolicyLayer and add a rule for search_by_query: 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 AI List My Business. Nothing to install.
search_by_query 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_by_query 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_by_query. 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_by_query is provided by the AI List My Business MCP server (mutamiri-sudo/ailistmybusiness). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →