get_municipality_data
AI agents call get_municipality_data to retrieve information from MLIT Data Platform MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and membership in a cohort of retrieval-only tools (get_data, get_data_catalog, get_prefecture_data, etc.) indicates this is a read operation that retrieves municipality data from Japan's MLIT platform. There is no evidence of creation, modification, deletion, code execution, or financial impact.
From the tool's definition Tool name 'get_municipality_data' and server description indicating 'natural language search and retrieval of data' with sibling tools all prefixed with 'get_' (get_all_data, get_count_data, get_data, etc.).
Attacks that exploit this kind of access
get_municipality_data. It is categorised as a Read tool in the MLIT Data Platform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MLIT Data Platform MCP Server MCP server in PolicyLayer and add a rule for get_municipality_data: 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 MLIT Data Platform MCP Server. Nothing to install.
get_municipality_data 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_municipality_data 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_municipality_data. 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_municipality_data is provided by the MLIT Data Platform MCP Server MCP server (kkawailab/kklab-mlit-dpf-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 →