get_nearby_amenities
AI agents call get_nearby_amenities to retrieve information from OneMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and server context, 'get_nearby_amenities' retrieves location-based amenity data without side effects. It follows the Read category pattern (get, fetch operations). No data modification, deletion, code execution, or financial operations are indicated. The low severity reflects that misuse would only expose queried location data, with minimal blast radius.
From the tool's definition Tool name 'get_nearby_amenities' indicates a retrieval operation. The server description confirms it provides 'location searches' and 'access to' various data layers without mentioning modifications, deletions, or external operations.
Attacks that exploit this kind of access
get_nearby_amenities. It is categorised as a Read tool in the OneMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OneMap MCP Server MCP server in PolicyLayer and add a rule for get_nearby_amenities: 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 OneMap MCP Server. Nothing to install.
get_nearby_amenities 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_nearby_amenities 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_nearby_amenities. 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_nearby_amenities is provided by the OneMap MCP Server MCP server (linzele/mcp-onemap). 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 →