// MCP TOOL REFERENCE

bulk_delete_forms

ServerTally MCP
CategoryDestructive

WHAT IT DOES

What bulk_delete_forms does on Tally MCP

AI agents call bulk_delete_forms to permanently remove resources in Tally MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why bulk_delete_forms needs a policy

Bulk deletion of forms cannot be undone and represents permanent data loss. Even though the tool now requires a confirmation workflow (confirm_bulk_delete), the underlying action is destructive. Destructive category takes precedence over Execute due to the irreversible nature of deletion. Critical severity due to potential for massive data loss across multiple forms in a single operation.

From the tool's definition Tool performs bulk deletion of forms ('bulk_delete_forms'). Description explicitly states it 'delete[s]' and is 'DEPRECATED' because it now requires confirmation before 'automatic execution'. The tool irreversibly removes data at scale.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control bulk_delete_forms

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 bulk_delete_forms:

policy.json

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

bulk_delete_forms 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 confirm_bulk_delete HUMAN CONFIRMATION: Confirm bulk deletion after reviewing preview. Requires explicit user 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 bulk_delete_forms

What does the bulk_delete_forms tool do? +

🚫 DEPRECATED: Use confirm_bulk_delete instead. This tool now requires human confirmation via the confirm_bulk_delete tool after preview_bulk_delete. The new workflow is: 1) preview_bulk_delete, 2) confirm_bulk_delete with user choice, 3) automatic execution. This tool is kept for backward compatibility but will reject calls without proper confirmation workflow. 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 bulk_delete_forms? +

Register the Tally MCP server in PolicyLayer and add a rule for bulk_delete_forms: 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 bulk_delete_forms? +

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

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

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

bulk_delete_forms 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 →

Free to start. No card required.

18 Tally MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.