remove-subscriber

Remove a subscriber from your publication by email or wallet address. This is a hard delete and cannot be undone — always confirm with the user before calling. Tip: call

Server Paragraph MCP paragraph-xyz/paragraph-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What remove-subscriber does on Paragraph MCP

AI agents call remove-subscriber to permanently remove resources in Paragraph MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove-subscriber needs a policy

This tool irreversibly deletes subscriber records with no undo capability. Although the blast radius is limited to subscriber account removal (not financial impact or broad data destruction), the permanent nature of the operation and the instruction to 'always confirm with the user before calling' classify it as Destructive rather than Write.

From the tool's definition Tool description states 'Remove a subscriber from your publication by email or wallet address. This is a hard delete and cannot be undone' — explicitly irreversible deletion of subscriber data.

Questions about remove-subscriber

What does the remove-subscriber tool do? +

Remove a subscriber from your publication by email or wallet address. This is a hard delete and cannot be undone — always confirm with the user before calling. Tip: call. It is categorised as a Destructive tool in the Paragraph MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove-subscriber? +

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

What risk level is remove-subscriber? +

remove-subscriber is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove-subscriber? +

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

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

remove-subscriber is provided by the Paragraph MCP server (paragraph-xyz/paragraph-mcp). 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.