Delete a comment by ID.
AI agents call comment.delete to permanently remove resources in Freedcamp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes comments, which is a destructive action that cannot be undone. While the blast radius is limited to individual comments (not system-wide), deletion of user-generated content is irreversible and represents a clear data destruction operation. This is more severe than Write (which is reversible) or Execute (which may have variable effects).
From the tool's definition Tool name and description: 'comment.delete' - 'Delete a comment by ID.' This explicitly performs an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a comment by ID. It is categorised as a Destructive tool in the Freedcamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for comment.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 Freedcamp MCP Server. Nothing to install.
comment.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 comment.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 comment.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.
comment.delete is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). 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 →