Delete your reef comment.
AI agents call delete_reef_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.
The tool performs an irreversible deletion operation on a comment. Even though the scope is limited to the user's own comments, deletion of data cannot be undone and fits the Destructive category by definition. Severity is high because an AI agent could maliciously delete user comments without recovery, damaging the user's participation history or content presence on the platform.
From the tool's definition Tool name contains 'delete' and description states 'Delete your reef comment' — irreversible deletion of user-generated content.
Attacks that exploit this kind of access
Delete your reef 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_reef_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_reef_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_reef_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_reef_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_reef_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.
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 →