delete_bot_data

THE RISK

Critical Risk

Why delete_bot_data needs a policy

This tool irreversibly deletes data (recordings, transcripts, and other bot-associated information) and cannot be undone. Deletion operations that remove data permanently fall into the Destructive category. While the blast radius is somewhat limited to a single bot's data rather than system-wide, the permanent loss of recordings and transcripts represents significant and irreversible harm.

From the tool's definition Tool name is 'delete_bot_data' and description states 'Delete all data associated with a bot (recordings, transcripts, etc.)' — uses the verb 'Delete' and describes irreversible removal of multiple data types including recordings and transcripts.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access delete_bot_data gives an agent:

POLICY

How to control delete_bot_data

PolicyLayer is an MCP gateway — it sits between your AI agents and Attendee MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_bot_data:

policy.json

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

delete_bot_data disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Attendee MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Attendee MCP Server tools

Destructive remove_meeting_bot Remove a bot from a meeting Execute create_meeting_bot Create a bot to join a meeting and record/transcribe it Execute make_bot_speak Make a bot speak text during a meeting using text-to-speech Execute send_video_to_meeting Send a video to the meeting through the bot (Google Meet only) Write send_chat_message Send a chat message from the bot to the meeting Write send_image_to_meeting Send an image to the meeting through the bot (Google Meet only) Read get_bot_status Get the current status of a meeting bot Read get_chat_messages Get chat messages from the meeting

All 11 Attendee MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Attendee MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_bot_data

What does the delete_bot_data tool do? +

Delete all data associated with a bot (recordings, transcripts, etc.). It is categorised as a Destructive tool in the Attendee 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_bot_data? +

Register the Attendee MCP Server MCP server in PolicyLayer and add a rule for delete_bot_data: 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 Attendee MCP Server. Nothing to install.

What risk level is delete_bot_data? +

delete_bot_data 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_bot_data? +

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

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

delete_bot_data is provided by the Attendee MCP Server MCP server (rexposadas/attendee-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Attendee MCP Server tool call.

Start from Attendee MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →