find_nearby_places
AI agents call find_nearby_places to retrieve information from ArcGIS Location Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location data (nearby places) without modifying, deleting, or executing external code. It is a Read operation with minimal blast radius—misuse would only surface incorrect location results, not cause data loss or financial harm. Confidence is slightly reduced due to missing tool description, but sibling context and naming are highly indicative.
From the tool's definition Tool name 'find_nearby_places' and sibling tools (geocode, reverse_geocode, get_directions, get_elevation, get_place_details) are all query/retrieval operations.
Attacks that exploit this kind of access
find_nearby_places. It is categorised as a Read tool in the ArcGIS Location Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS Location Services MCP Server MCP server in PolicyLayer and add a rule for find_nearby_places: 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 ArcGIS Location Services MCP Server. Nothing to install.
find_nearby_places 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 find_nearby_places 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 find_nearby_places. 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.
find_nearby_places is provided by the ArcGIS Location Services MCP Server MCP server (lwsinclair/arcgis-location-services-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 →