AI agents call get_earthquake_details to retrieve information from Mcp Swiss 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 seismic event information from the Swiss Seismological Service database. It has no side effects—it only queries and returns data. No data is created, modified, deleted, or overwritten. No external commands are executed. The blast radius of misuse is minimal; an agent could at worst retrieve seismic data it shouldn't see, but cannot damage systems or data.
From the tool's definition Tool name 'get_earthquake_details' and description 'Get full details for a specific seismic event' indicate data retrieval.
Attacks that exploit this kind of access
Get full details for a specific seismic event by its SED (Swiss Seismological Service) event ID. It is categorised as a Read tool in the Mcp Swiss MCP Server, which means it retrieves data without modifying state.
Register the Mcp Swiss MCP server in PolicyLayer and add a rule for get_earthquake_details: 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 Swiss. Nothing to install.
get_earthquake_details 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_earthquake_details 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_earthquake_details. 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_earthquake_details is provided by the Mcp Swiss MCP server (mcp-swiss). 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 →