confirm_bulk_delete

THE RISK

Critical Risk

Why confirm_bulk_delete needs a policy

Bulk deletion of forms is an irreversible operation that destroys data at scale. Even with human confirmation required, this remains a Destructive category tool. Severity is high because a single misuse could eliminate many forms, though the confirmation requirement prevents accidental triggering by an unaligned agent.

From the tool's definition Tool name contains 'bulk_delete' and description states it 'Confirm bulk deletion' — this irreversibly removes multiple forms. The requirement for 'explicit user choice' mitigates risk somewhat but does not change the destructive nature of the operation.

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

POLICY

How to control confirm_bulk_delete

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

policy.json

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

confirm_bulk_delete 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 Tally MCP — 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 Tally MCP tools

Destructive bulk_delete_forms 🚫 DEPRECATED: Use confirm_bulk_delete instead. This tool now requires human confirmation Destructive delete_form Delete a Tally form permanently Execute diagnostic_tool Runs diagnostic checks on the application. Write create_form Create a new Tally form with specified fields and configuration. This tool converts simple Write generate_template Generate a form template based on requirements or use case Write manage_team Manage team members and permissions Write manage_workspace Manage workspace settings and information Write modify_form Modify an existing Tally form

All 18 Tally MCP 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 Tally MCP → 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 confirm_bulk_delete

What does the confirm_bulk_delete tool do? +

HUMAN CONFIRMATION: Confirm bulk deletion after reviewing preview. Requires explicit user choice from options provided. It is categorised as a Destructive tool in the Tally MCP 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 confirm_bulk_delete? +

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

What risk level is confirm_bulk_delete? +

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

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

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

confirm_bulk_delete is provided by the Tally MCP server (learnwithcc/tally-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tally MCP tool call.

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

CHECK YOUR STACK →