layout_delete

THE RISK

Critical Risk

Why layout_delete needs a policy

The tool permanently removes a layout object from persistent storage with no undo or recovery mechanism implied. This is a destructive operation that cannot be undone. Severity is high rather than critical because the blast radius is limited to a single layout artifact rather than cascading system-wide damage, though loss of engineering diagrams could impact project continuity.

From the tool's definition Tool name 'layout_delete' and description 'Delete a layout from the store' indicate irreversible deletion of data.

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

POLICY

How to control layout_delete

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

policy.json

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

layout_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 Engineering MCP Server — 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 Engineering MCP Server tools

Execute layout_compute Compute layout for a model using ELK. Produces orthogonal edge routing suitable for P&ID d Execute model_batch_apply Execute multiple operations in a single call for efficiency Execute rules_apply Apply validation rules and return structured issues for LLM processing. Optionally auto-fi Write area_deploy Deploy a template into a model (STRATEGIC operation - replaces 50+ atomic calls) Write model_tx_begin Start a transaction on a model for atomic multi-operation changes Write model_combine Merge multiple DEXPI models into one combined model. Combines all tagged plant items, inst Write model_load Import a model from various formats (JSON, Proteus XML, SFILES string) - Replaces dexpi_im Write project_init Initialize a new git-tracked project for engineering models

All 72 Engineering MCP Server 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 Engineering MCP Server → 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 layout_delete

What does the layout_delete tool do? +

Delete a layout from the store. It is categorised as a Destructive tool in the Engineering MCP Server 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 layout_delete? +

Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for layout_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 Engineering MCP Server. Nothing to install.

What risk level is layout_delete? +

layout_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 layout_delete? +

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

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

layout_delete is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Engineering MCP Server tool call.

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

CHECK YOUR STACK →