Mendapatkan daftar semua kelurahan/desa dalam kecamatan tertentu dari database lokal.
AI agents call get_villages_in_district 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 a list of villages and hamlets within a district from a local database. It performs no data modification, deletion, code execution, or financial operations. It is a straightforward query operation that returns pre-existing location information, consistent with other Read-category tools on this server like search_location_code.
From the tool's definition Tool description states "Mendapatkan daftar semua kelurahan/desa dalam kecamatan tertentu dari database lokal" (Get list of all villages/hamlets in a specific district from local database).
Attacks that exploit this kind of access
Mendapatkan daftar semua kelurahan/desa dalam kecamatan tertentu dari database lokal. 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 get_villages_in_district: 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.
get_villages_in_district 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_villages_in_district 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_villages_in_district. 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_villages_in_district 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 →