Remove a canonical tag mapping.
AI agents call canonical_tag_remove to permanently remove resources in Vector Task MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes (deletes) a canonical tag mapping, which is a destructive operation that cannot be undone. The action permanently eliminates stored tag configuration data. While the blast radius is limited to tag metadata rather than user tasks themselves, the irreversible nature of deletion makes this Destructive rather than Write.
From the tool's definition Tool name 'canonical_tag_remove' and description 'Remove a canonical tag mapping' indicate irreversible deletion of tag metadata.
Attacks that exploit this kind of access
Remove a canonical tag mapping. It is categorised as a Destructive tool in the Vector Task MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vector Task MCP Server MCP server in PolicyLayer and add a rule for canonical_tag_remove: 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 Vector Task MCP Server. Nothing to install.
canonical_tag_remove 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 canonical_tag_remove 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 canonical_tag_remove. 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.
canonical_tag_remove is provided by the Vector Task MCP Server MCP server (xsaven/vector-task-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 →