delete_reef_post

Delete your reef post.

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-reef-post.md

WHAT IT DOES

What delete_reef_post does on Basis MCP Server

AI agents call delete_reef_post 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.

RISK

Why delete_reef_post is rated Critical

The tool permanently removes a post, which is a destructive action that cannot be undone. While the scope is limited to the user's own post (not arbitrary data across the system), deletion is irreversible. High severity reflects the fact that an AI agent with access could accidentally or maliciously wipe out user content if misdirected or if the user's intention is misinterpreted.

From the tool's definition Tool name contains 'delete' and description states 'Delete your reef post' — explicit irreversible destruction of user-generated content.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_reef_post 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_reef_post, this is the rule to start with:

delete_reef_post Hidden

delete_reef_post is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_reef_post"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every delete_reef_post call is checked against it from then on.

FAQ

Questions about delete_reef_post

What does the delete_reef_post tool do? +

Delete your reef post. 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_reef_post? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for delete_reef_post: 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_reef_post? +

delete_reef_post 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_reef_post? +

Yes. Add a rate_limit block to the delete_reef_post 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_reef_post completely? +

Set action: deny in the PolicyLayer policy for delete_reef_post. 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_reef_post? +

delete_reef_post 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.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →