New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_project_comment

Delete a project comment.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_project_comment

What does the delete_project_comment tool do? +

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.

How do I enforce a policy on delete_project_comment? +

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.

What risk level is delete_project_comment? +

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.

Can I rate-limit delete_project_comment? +

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.

How do I block delete_project_comment completely? +

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.

What MCP server provides delete_project_comment? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Basis MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.