get_search_results
AI agents call get_search_results to retrieve information from Infobel Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search query to retrieve business records from the Infobel GetData API. No side effects or data modifications are implied by the name or server context. This is a straightforward read operation with minimal risk—an AI agent misusing it would retrieve unwanted data but cannot alter, delete, or execute operations.
From the tool's definition Tool name 'get_search_results' indicates retrieval of data. Server description states it enables 'search businesses, retrieve records, and browse categories and locations.' Sibling tools (get_available_countries, get_cities, get_currencies, etc.) are all…
Attacks that exploit this kind of access
get_search_results. It is categorised as a Read tool in the Infobel Api MCP Server, which means it retrieves data without modifying state.
Register the Infobel Api MCP server in PolicyLayer and add a rule for get_search_results: 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 Infobel Api. Nothing to install.
get_search_results 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 get_search_results 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 get_search_results. 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.
get_search_results is provided by the Infobel Api MCP server (techinfobel/infobel-getdata-api-mcp). 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 →