AI agents call qem to retrieve information from Mcp Hko without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or current earthquake message data with no ability to modify, delete, or execute external operations. It is a read-only query of weather/earthquake information provided by a public meteorological service. The 'lang' parameter suggests it may filter results by language but does not enable any side effects.
From the tool's definition The tool is named 'Quick Earthquake Messages (qem) API Request' and is part of a weather data retrieval service alongside tools like 'feltearthquake', 'hourlyrainfall', and other forecast/data retrieval endpoints.
Attacks that exploit this kind of access
Quick Earthquake Messages (qem) API Request Parameters: - lang:. It is categorised as a Read tool in the Mcp Hko MCP Server, which means it retrieves data without modifying state.
Register the Mcp Hko MCP server in PolicyLayer and add a rule for qem: 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 Mcp Hko. Nothing to install.
qem 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 qem 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 qem. 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.
qem is provided by the Mcp Hko MCP server (louiscklaw/mcp-hko). 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 →