Critical Risk →

delete_form

Delete a Tally form permanently

How to control delete_form ↓

What delete_form does on Tally MCP

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

Critical Risk

Why delete_form needs a policy

This tool irreversibly deletes data (a Tally form) and cannot be reversed. Destructive category applies to actions that cannot be undone. The severity is high because deletion of user-created forms represents significant data loss, though the blast radius is limited to individual forms rather than entire systems. Confidence is high due to explicit 'permanently' language in the description.

From the tool's definition Tool description states 'Delete a Tally form permanently' - the word 'permanently' combined with 'delete' indicates irreversible data destruction. The tool name 'delete_form' and description confirm this action cannot be undone.

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

How to control delete_form

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

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

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

  1. Create a free account and register Tally MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_form

What does the delete_form tool do? +

Delete a Tally form permanently. 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 delete_form? +

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

delete_form 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_form? +

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.