Critical Risk →

attrove_delete_meeting

Reversibly archive (soft-delete) a meeting from the user

Part of the Attrove server.

attrove_delete_meeting can permanently delete data in Attrove, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ATTROVE →

Free to start. No card required.

AI agents may call attrove_delete_meeting to permanently remove or destroy resources in Attrove. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call attrove_delete_meeting in a loop, permanently destroying resources in Attrove. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "attrove_delete_meeting"
  ]
}

See the full Attrove policy for all 17 tools.

Get this rule live on your own Attrove server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ATTROVE →

View all 17 tools →

These attack patterns abuse exactly the kind of access attrove_delete_meeting gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so attrove_delete_meeting only ever does what you allow.

SECURE ATTROVE →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the attrove_delete_meeting tool do? +

Reversibly archive (soft-delete) a meeting from the user. It is categorised as a Destructive tool in the Attrove 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 attrove_delete_meeting? +

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

What risk level is attrove_delete_meeting? +

attrove_delete_meeting 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 attrove_delete_meeting? +

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

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

attrove_delete_meeting is provided by the Attrove MCP server (@attrove/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Attrove tool call.

Deterministic rules across all 17 Attrove tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.