東京都内の全WBGT観測地点の予測値を一括取得します
AI agents call get_all_tokyo_locations to retrieve information from Tokyo WBGT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation that queries and returns WBGT heat index forecast data for Tokyo locations. It has no side effects, does not modify or delete data, does not execute code or commands, and involves no financial operations. It is purely informational/read access to a public heat safety dataset provided by Japan's Ministry of the Environment.
From the tool's definition Tool name 'get_all_tokyo_locations' and description indicate batch retrieval of WBGT forecast predictions ('予測値を一括取得します' = 'retrieve forecast values in bulk') from multiple observation points.
Attacks that exploit this kind of access
東京都内の全WBGT観測地点の予測値を一括取得します. It is categorised as a Read tool in the Tokyo WBGT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tokyo WBGT MCP Server MCP server in PolicyLayer and add a rule for get_all_tokyo_locations: 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 Tokyo WBGT MCP Server. Nothing to install.
get_all_tokyo_locations 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_all_tokyo_locations 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_all_tokyo_locations. 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_all_tokyo_locations is provided by the Tokyo WBGT MCP Server MCP server (yukit7s/cc-get-wbgt). 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 →