Critical Risk →

remove_named_range

Remove a named range from an Excel file

Part of the Xlsx server.

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

SECURE XLSX →

Free to start. No card required.

AI agents may call remove_named_range to permanently remove or destroy resources in Xlsx. 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 remove_named_range in a loop, permanently destroying resources in Xlsx. 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": [
    "remove_named_range"
  ]
}

See the full Xlsx policy for all 7 tools.

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

ENFORCE ON MY XLSX →

These attack patterns abuse exactly the kind of access remove_named_range 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 remove_named_range only ever does what you allow.

SECURE XLSX →

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

What does the remove_named_range tool do? +

Remove a named range from an Excel file. It is categorised as a Destructive tool in the Xlsx 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 remove_named_range? +

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

What risk level is remove_named_range? +

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

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

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

remove_named_range is provided by the Xlsx MCP server (xlsx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xlsx tool call.

Deterministic rules across all 7 Xlsx 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.