Remove a tag (DELETE /tags/{id}). Voog returns 204.
AI agents call tag_delete to permanently remove resources in Voog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
tag_delete performs an irreversible deletion operation on tags in the Voog CMS system. Deletion cannot be undone and results in data loss. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' Severity is high because unintended tag deletion could disrupt content organization and SEO structure across the CMS,…
From the tool's definition Tool description explicitly states 'Remove a tag' with DELETE HTTP method, which irreversibly deletes data. The HTTP 204 response confirms successful deletion with no recovery path.
Attacks that exploit this kind of access
Remove a tag (DELETE /tags/{id}). Voog returns 204. It is categorised as a Destructive tool in the Voog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Voog MCP server in PolicyLayer and add a rule for tag_delete: 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 Voog. Nothing to install.
tag_delete 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 tag_delete 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 tag_delete. 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.
tag_delete is provided by the Voog MCP server (runnel/voog-mcp). 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 →