Usgs Earthquakes

33 tools. 11 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

11 can modify or destroy data
22 read-only
33 tools total

Verified server · catalogue entry verified 02/07/2026 · full schemas captured for 33 of 33 tools

How to control Usgs Earthquakes ↓

What Usgs Earthquakes exposes to your agents

Read (22) Write / Execute (7) Destructive / Financial (4)

What Usgs Earthquakes costs in tokens

11,426 tokens of tool definitions, loaded on every request
5.7% of a 200k context window
1,084 heaviest tool: bet_research
Critical Risk

The most dangerous Usgs Earthquakes tools

11 of Usgs Earthquakes's 33 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Usgs Earthquakes

PolicyLayer is an MCP gateway — it sits between your AI agents and Usgs Earthquakes, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "polymarket_arbitrage": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
{
  "forget": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "generate_llms_txt": {
    "limits": [
      {
        "counter": "generate_llms_txt_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "ask_pipeworx": {
    "limits": [
      {
        "counter": "ask_pipeworx_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Usgs Earthquakes — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON USGS EARTHQUAKES →

Instant setup, no code required.

All 33 Usgs Earthquakes tools

READ 22 tools
Read ask_pipeworx PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS ec Read ask_pipeworx_grounded Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool Read bet_research Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will- Read compare_entities "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank th Read count_earthquakes Count earthquakes matching a filter without returning the events — fast for questions like "how many M5+ quake Read deep_research ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan) Read discover_tools Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tool Read entity_profile "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Micros Read get_earthquake Get full detail for a single earthquake by its USGS event id (e.g. "us7000n7n8"). Returns magnitude, location, Read list_subscriptions List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for ea Read pipeworx_trending What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volum Read polymarket_kalshi_spread Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes pri Read recall Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up Read recent_alerts Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to you Read recent_changes "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / " Read resolve_entity "What's the ticker for…" / "find the CIK for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X' Read scan_competitor_ai_presence Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) w Read scan_dependency Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license Read search_earthquakes Search the USGS earthquake catalog (FDSNWS event API) for real-time and historical seismic events. Filter by t Read search_within Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a Read suggest_questions What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / Read validate_claim "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Usgs Earthquakes

Can an AI agent move money through the Usgs Earthquakes MCP server? +

Yes. The Usgs Earthquakes server exposes 3 financial tools including polymarket_arbitrage, polymarket_edge_tracker, polymarket_edges. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Usgs Earthquakes MCP server? +

Yes. The Usgs Earthquakes server exposes 1 destructive tools including forget. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Usgs Earthquakes? +

The Usgs Earthquakes server has 6 write tools including generate_llms_txt, pipeworx_feedback, polymarket_fill_risk. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Usgs Earthquakes.

How many tools does the Usgs Earthquakes MCP server expose? +

33 tools across 3 categories: Destructive, Read, Write. 22 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Usgs Earthquakes? +

Register the Usgs Earthquakes MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Usgs Earthquakes tool call.

Deterministic rules across all 33 Usgs Earthquakes tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

33 Usgs Earthquakes tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.