Critical Risk →

bulk_delete_models

Bulk delete closed models (WARNING: irreversible). Models must be closed first.

How to control bulk_delete_models ↓

What bulk_delete_models does on Anaplan MCP

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

Critical Risk

Why bulk_delete_models needs a policy

This tool permanently removes models without the possibility of recovery. The irreversibility and bulk nature create maximum blast radius; accidental or malicious invocation would result in unrecoverable data loss. This is the most severe category of risk.

From the tool's definition Tool name 'bulk_delete_models' combined with description explicitly stating 'Bulk delete closed models (WARNING: irreversible)' — the word 'irreversible' is definitive.

Risk signalsBulk/mass operation — affects multiple targets

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

How to control bulk_delete_models

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

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

bulk_delete_models 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 Anaplan 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 bulk_delete_models

What does the bulk_delete_models tool do? +

Bulk delete closed models (WARNING: irreversible). Models must be closed first. It is categorised as a Destructive tool in the Anaplan 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_models? +

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

What risk level is bulk_delete_models? +

bulk_delete_models 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_models? +

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

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

bulk_delete_models is provided by the Anaplan MCP server (larasrinath/anaplan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Anaplan MCP tool call.

Start from Anaplan 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.

70 Anaplan 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.