search_location_code
AI agents call search_location_code to retrieve information from BMKG 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 or searches for location codes—a read-only query operation with no data modification, deletion, or execution capabilities. No blast radius from misuse; worst case is returning irrelevant or no results. Confidence is 0.85 rather than higher because the empty description leaves some ambiguity, but the tool name and server context provide strong contextual evidence.
From the tool's definition Tool name 'search_location_code' indicates a lookup/search operation. Sibling tools (get_felt_earthquakes, get_latest_earthquake, get_villages_in_district, get_weather_forecast, etc.) are all retrieval-based Read operations, establishing this server's pattern…
Attacks that exploit this kind of access
search_location_code. It is categorised as a Read tool in the BMKG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BMKG MCP Server MCP server in PolicyLayer and add a rule for search_location_code: 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 BMKG MCP Server. Nothing to install.
search_location_code 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_location_code 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_location_code. 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_location_code is provided by the BMKG MCP Server MCP server (revomkg/mcp-bmkg). 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 →