AI agents call search_earthquakes_by_location 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 queries a public seismic data service to retrieve historical or real-time earthquake information. It performs no modifications, deletions, or external operations—only data retrieval. No authentication required (zero API keys per server description). Misuse poses minimal risk; worst case is information disclosure of already-public seismic data.
From the tool's definition Tool name 'search_earthquakes_by_location' and description 'Search for earthquakes' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for earthquakes near a geographic location using the Swiss Seismological Service (SED) FDSN API. 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 search_earthquakes_by_location: 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.
search_earthquakes_by_location 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 search_earthquakes_by_location 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 search_earthquakes_by_location. 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.
search_earthquakes_by_location 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 →