Delete a custom status. Tasks with this status will be reverted to
AI agents call quire.deleteStatus 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.
Deleting a custom status is irreversible and has cascading effects across all tasks using that status. The description confirms tasks will be affected (reverted), making this a destructive operation with potentially wide blast radius across a project's task management structure.
From the tool's definition Tool name 'deleteStatus' and description 'Delete a custom status. Tasks with this status will be reverted to' — explicitly deletes a custom status and causes cascading side effects on tasks.
Attacks that exploit this kind of access
Delete a custom status. Tasks with this status will be reverted to. 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.deleteStatus: 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.deleteStatus 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.deleteStatus 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.deleteStatus. 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.deleteStatus 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 →