usgs-eq-count

Return the number of USGS earthquake events matching a filter (no payload).

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/usgs-eq-count.md

WHAT IT DOES

What usgs-eq-count does on Meta Data Mcp

AI agents call usgs-eq-count to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why usgs-eq-count is rated Low

This tool performs a read-only query against USGS earthquake data and returns a count. It has no side effects, does not modify data, and cannot execute code or delete information. The '(no payload)' note confirms no data is being written. Even if misused by an AI agent, returning an incorrect filter would only retrieve wrong count data, with no destructive consequences.

From the tool's definition Tool is called 'usgs-eq-count' and described as 'Return the number of USGS earthquake events matching a filter (no payload)' — it queries and retrieves aggregated data without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs usgs-eq-count safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usgs-eq-count, this is the rule to start with:

usgs-eq-count Allowed

usgs-eq-count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "usgs-eq-count": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every usgs-eq-count call is checked against it from then on.

FAQ

Questions about usgs-eq-count

What does the usgs-eq-count tool do? +

Return the number of USGS earthquake events matching a filter (no payload). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on usgs-eq-count? +

Register the Meta Data MCP server in PolicyLayer and add a rule for usgs-eq-count: 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 Meta Data Mcp. Nothing to install.

What risk level is usgs-eq-count? +

usgs-eq-count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit usgs-eq-count? +

Yes. Add a rate_limit block to the usgs-eq-count 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.

How do I block usgs-eq-count completely? +

Set action: deny in the PolicyLayer policy for usgs-eq-count. 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.

What MCP server provides usgs-eq-count? +

usgs-eq-count is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →