search_poi_polygon
AI agents call search_poi_polygon to retrieve information from Amap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_poi_polygon' combined with context that this is a geographic information service suggests it retrieves POI (Points of Interest) data within polygon boundaries. This is a read-only query operation with no data modification, execution, or destructive effects. The empty description prevents higher confidence, but the naming pattern and server purpose strongly indicate a read operation.
From the tool's definition Tool name 'search_poi_polygon' and sibling tools (geocoding, reverse_geocoding, POI searches) indicate data retrieval functionality. Description is empty, reducing confidence.
Attacks that exploit this kind of access
search_poi_polygon. It is categorised as a Read tool in the Amap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amap MCP Server MCP server in PolicyLayer and add a rule for search_poi_polygon: 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 Amap MCP Server. Nothing to install.
search_poi_polygon 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_poi_polygon 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_poi_polygon. 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_poi_polygon is provided by the Amap MCP Server MCP server (qiao101660/gaode_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 →