get_count_data
AI agents call get_count_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 tool name and context strongly indicate this retrieves/queries count data from the MLIT platform without side effects. The empty description lowers confidence slightly, but the pattern of sibling tools (all read-only) and the server's stated purpose (retrieval, search) make misclassification unlikely. Even if invoked incorrectly, it only returns data counts with minimal blast radius.
From the tool's definition Tool name 'get_count_data' suggests data retrieval; sibling tools (get_all_data, get_data, get_data_catalog, get_data_summary, get_municipality_data, get_prefecture_data) are all Read operations.
Attacks that exploit this kind of access
get_count_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_count_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_count_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_count_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_count_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_count_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 →