p2pquake.seismic.tsunami_warnings

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/p2pquake.seismic.tsunami-warnings.md

WHAT IT DOES

What p2pquake.seismic.tsunami_warnings does on Apibase

AI agents use p2pquake.seismic.tsunami_warnings to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`limit`	integer	—	Number of tsunami events to return (default 10, max 100)
`order`	integer	—	Sort direction: -1 for newest-first (default), 1 for oldest-first
`offset`	integer	—	Pagination offset (0-based, default 0)

Parameters from the server's own tool schema.

RISK

Why p2pquake.seismic.tsunami_warnings is rated Medium

An AI agent can call p2pquake.seismic.tsunami_warnings faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs p2pquake.seismic.tsunami_warnings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For p2pquake.seismic.tsunami_warnings, this is the rule to start with:

p2pquake.seismic.tsunami_warnings Rate-limited

p2pquake.seismic.tsunami_warnings stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "p2pquake.seismic.tsunami_warnings": {
      "limits": [
        {
          "counter": "p2pquake.seismic.tsunami_warnings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every p2pquake.seismic.tsunami_warnings call is checked against it from then on.

FAQ

Questions about p2pquake.seismic.tsunami_warnings

What does the p2pquake.seismic.tsunami_warnings tool do? +

Get current and recent tsunami warning/advisory bulletins issued by JMA via the P2PQuake network. Returns warning grade per coastal area (MajorWarning/Warning/Watch), immediate-danger flag, estimated wave height, expected first-arrival time, and the triggering earthquake details. Cancelled bulletins are included with cancelled=true for audit trails. Coverage: all Pacific, Sea of Japan, and Inland Sea coastal areas of Japan. Typical warning lifecycle: FirstReport → Update → AllClear. Use this tool for real-time tsunami monitoring in Japan. Data source: P2PQuake — community-operated JMA relay, open data, no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does p2pquake.seismic.tsunami_warnings accept? +

p2pquake.seismic.tsunami_warnings accepts 3 parameters: limit, order, offset. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on p2pquake.seismic.tsunami_warnings? +

Register the Apibase MCP server in PolicyLayer and add a rule for p2pquake.seismic.tsunami_warnings: 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 Apibase. Nothing to install.

What risk level is p2pquake.seismic.tsunami_warnings? +

p2pquake.seismic.tsunami_warnings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit p2pquake.seismic.tsunami_warnings? +

Yes. Add a rate_limit block to the p2pquake.seismic.tsunami_warnings 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 p2pquake.seismic.tsunami_warnings completely? +

Set action: deny in the PolicyLayer policy for p2pquake.seismic.tsunami_warnings. 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 p2pquake.seismic.tsunami_warnings? +

p2pquake.seismic.tsunami_warnings is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →