東京都の実測WBGT値を取得します（実測地点のみ）
AI agents call get_tokyo_realtime_data 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 tool queries and returns existing WBGT measurement data from Tokyo's observation network. It performs a read-only operation with no side effects, no data modification, no code execution, and no financial impact. The low severity reflects that misuse would only result in retrieving public health/safety data without operational consequences.
From the tool's definition Tool name contains 'get_' and description states '実測WBGT値を取得します' (retrieves measured WBGT values). The tool retrieves real-time heat index data from observation points with no modification, deletion, or execution of external operations.
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_tokyo_realtime_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 Tokyo WBGT MCP Server. Nothing to install.
get_tokyo_realtime_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_tokyo_realtime_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_tokyo_realtime_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_tokyo_realtime_data 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 →