Delete a tag from Systeme.io. This removes the tag from all contacts.
AI agents call delete_tag to permanently remove resources in Systemeio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation that affects all contacts tagged with the target tag. Once deleted, the tag cannot be recovered and the association is permanently removed from potentially many contacts. This qualifies as Destructive rather than Write because the action cannot be undone. The blast radius is significant as it impacts all tagged contacts at once, justifying 'high' severity.
From the tool's definition Tool name is 'delete_tag' and description states it 'Delete a tag from Systeme.io. This removes the tag from all contacts.' The verb 'delete' combined with 'removes the tag from all contacts' indicates irreversible removal of data across multiple records.
Attacks that exploit this kind of access
Delete a tag from Systeme.io. This removes the tag from all contacts. It is categorised as a Destructive tool in the Systemeio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Systemeio MCP server in PolicyLayer and add a rule for delete_tag: 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 Systemeio. Nothing to install.
delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_tag 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 delete_tag. 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.
delete_tag is provided by the Systemeio MCP server (snzeeee/mcp-server-systemeio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →