list_subscriptions

List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

Server Usgs Earthquakes pipeworx-io/mcp-usgs-earthquakes
Category Read
Risk class Low
Parameters 10 required

What list_subscriptions does on Usgs Earthquakes

AI agents call list_subscriptions to retrieve information from Usgs Earthquakes without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
include_inactive boolean Include cancelled subscriptions in the response (default false).

Parameters from the server's own tool schema.

Why list_subscriptions needs a policy

This tool retrieves and displays subscription metadata belonging to the user. It has no side effects—it only queries and returns existing data. The description explicitly frames it as a review/lookup mechanism ('Use this to review what you're monitoring'). No data is created, modified, deleted, or executed. This is a straightforward read operation with minimal security risk.

From the tool's definition Tool description states 'List the caller's active subscriptions' and 'Returns id, type, params, created_at, last_fired_at, fire_count for each.' These are purely informational queries with no modification or deletion capability.

Questions about list_subscriptions

What does the list_subscriptions tool do? +

List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel. It is categorised as a Read tool in the Usgs Earthquakes MCP Server, which means it retrieves data without modifying state.

What parameters does list_subscriptions accept? +

list_subscriptions accepts 1 parameter: include_inactive. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_subscriptions? +

Register the Usgs Earthquakes MCP server in PolicyLayer and add a rule for list_subscriptions: 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 Usgs Earthquakes. Nothing to install.

What risk level is list_subscriptions? +

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

Can I rate-limit list_subscriptions? +

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

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

list_subscriptions is provided by the Usgs Earthquakes MCP server (pipeworx-io/mcp-usgs-earthquakes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.