Search for locations matching specific criteria
AI agents call search_locations to retrieve information from People Data Labs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries location data and returns results. No data is created, modified, deleted, or executed. It is a standard read/search operation consistent with the other sibling tools on the server (e.g., search_people, search_companies, search_job_titles), which are all data retrieval functions.
From the tool's definition Tool is named 'search_locations' and described as 'Search for locations matching specific criteria' — a query operation with no side effects. It retrieves data without modifying, deleting, or executing external code.
Attacks that exploit this kind of access
Search for locations matching specific criteria. It is categorised as a Read tool in the People Data Labs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the People Data Labs MCP Server MCP server in PolicyLayer and add a rule for search_locations: 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 People Data Labs MCP Server. Nothing to install.
search_locations 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_locations 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_locations. 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_locations is provided by the People Data Labs MCP Server MCP server (phxdev1/peopledatalabs-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 →