New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_subscriber_note

Delete one internal subscriber note by note ID.

SERVERSequenzy Mcp SOURCESequenzy/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/delete-subscriber-note.md

What delete_subscriber_note does on Sequenzy Mcp

AI agents call delete_subscriber_note to permanently remove resources in Sequenzy Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_subscriber_note is rated Critical

Deletion of data records is inherently irreversible and cannot be undone without external backups. While the blast radius is limited to a single note rather than bulk data, the permanent loss of information (internal notes may contain important context, compliance records, or customer interactions) qualifies this as a Destructive action.

From the tool's definition Tool performs 'Delete' operation on 'subscriber note' by ID, with no indication of recovery, restoration, or soft-delete mechanism. Description explicitly uses the irreversible verb 'Delete'.

Questions about delete_subscriber_note

What does the delete_subscriber_note tool do? +

Delete one internal subscriber note by note ID. It is categorised as a Destructive tool in the Sequenzy 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 delete_subscriber_note? +

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

What risk level is delete_subscriber_note? +

delete_subscriber_note 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 delete_subscriber_note? +

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

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

delete_subscriber_note is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sequenzy, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sequenzy's. Pull the full record:

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.