Delete a comment. This action cannot be undone.
AI agents call quire.deleteComment 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.
Deletion of comments is an irreversible operation with no undo capability. While the blast radius may be limited to a single comment rather than an entire dataset, the permanent nature of the action and the lack of recovery options place this firmly in the Destructive category, which takes precedence over Write operations.
From the tool's definition Tool name 'deleteComment' and description explicitly states 'Delete a comment. This action cannot be undone.' The irreversible deletion of data is the defining characteristic of Destructive.
Attacks that exploit this kind of access
Delete a comment. This action cannot be undone. 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.deleteComment: 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.deleteComment 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.deleteComment 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.deleteComment. 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.deleteComment 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 →