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.
This record as markdown: /tools/io-github-pipeworx-io-19hz/list-subscriptions.md
What list_subscriptions does on 19hz
AI agents call list_subscriptions to retrieve information from 19hz without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
include_inactive | boolean | — | Include cancelled subscriptions in the response (default false). |
Parameters from the server's own tool schema.
Why list_subscriptions is rated Low
This tool retrieves and displays existing subscription data without creating, modifying, or deleting anything. It is a read-only query operation with no side effects. The low severity reflects that misuse would only expose existing subscription information to the caller, not expose other users' data or enable unauthorized actions.
From the tool's definition Tool description explicitly states 'List the caller's active subscriptions' and returns metadata fields (id, type, params, created_at, last_fired_at, fire_count).
Attacks that exploit this kind of access
The rule that runs list_subscriptions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_subscriptions, this is the rule to start with:
list_subscriptions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every list_subscriptions call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
list_subscriptions accepts 1 parameter: include_inactive. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz 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 19hz. Nothing to install.
list_subscriptions 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 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.
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.
list_subscriptions is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue