unsubscribe
Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
This record as markdown: /tools/io-github-pipeworx-io-19hz/unsubscribe.md
What unsubscribe does on 19hz
AI agents use unsubscribe to create or update resources in 19hz, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 19hz environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Subscription id (uuid) returned by subscribe. |
Parameters from the server's own tool schema.
Why unsubscribe is rated Medium
The tool cancels/deactivates a subscription record but explicitly states the row is not deleted, preserving historical data. This is a reversible modification (Write), not Destructive. However, cancelling a subscription could have service-access implications, raising severity to medium. It does not move money or execute code.
From the tool's definition 'Cancel a subscription by id' and 'The row is deactivated (not deleted)' — the action is reversible deactivation, not permanent deletion
Attacks that exploit this kind of access
The rule that runs unsubscribe 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 unsubscribe, this is the rule to start with:
unsubscribe 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every unsubscribe call is checked against it from then on.
Questions about unsubscribe
Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts. It is categorised as a Write tool in the 19hz MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unsubscribe accepts 1 parameter: id. Required: id. 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 unsubscribe: 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.
unsubscribe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unsubscribe 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 unsubscribe. 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.
unsubscribe 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