delete_project_comment
Delete a project comment.
This record as markdown: /tools/launch-on-basis-mcp-ts/delete-project-comment.md
What delete_project_comment does on Basis MCP Server
AI agents call delete_project_comment to permanently remove resources in Basis MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_project_comment is rated Critical
This tool permanently removes a project comment, which cannot be undone. Destructive operations that erase data are the most severe category. While the blast radius is limited to a single comment (not financial impact or system-wide data loss), the irreversibility and user-facing consequences warrant 'high' severity. Confidence is high because the deletion semantics are unambiguous.
From the tool's definition Tool name explicitly uses 'delete', and description states 'Delete a project comment.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_project_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_project_comment, this is the rule to start with:
delete_project_comment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every delete_project_comment call is checked against it from then on.
Questions about delete_project_comment
Delete a project comment. It is categorised as a Destructive tool in the Basis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for delete_project_comment: 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 Basis MCP Server. Nothing to install.
delete_project_comment 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 delete_project_comment 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 delete_project_comment. 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.
delete_project_comment is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
Across the catalogue