Delete a tag. This will remove the tag from all tasks that have it.
AI agents call quire.deleteTag to permanently remove resources in Quire MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a tag and removes it from all associated tasks. Tag deletion cannot be undone and impacts the organization/categorization of tasks throughout the project. While not deleting individual tasks, it is a destructive operation that eliminates data structure with broad scope, warranting the Destructive category and high severity.
From the tool's definition Tool name 'deleteTag' and description states 'Delete a tag. This will remove the tag from all tasks that have it.' The operation is irreversible and affects multiple tasks across the project.
Attacks that exploit this kind of access
Delete a tag. This will remove the tag from all tasks that have it. It is categorised as a Destructive tool in the Quire MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Quire MCP Server MCP server in PolicyLayer and add a rule for quire.deleteTag: 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 Quire MCP Server. Nothing to install.
quire.deleteTag 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 quire.deleteTag 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 quire.deleteTag. 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.
quire.deleteTag is provided by the Quire MCP Server MCP server (jacob-hartmann/quire-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 →