layout_compute

THE RISK

High Risk

Why layout_compute needs a policy

This tool runs an external computation (ELK layout engine) on a model to produce routing results. It does not simply read static data nor does it directly persist/modify stored diagrams, but it executes a computational process whose output depends on the input model. It qualifies as Execute since it triggers an external operation (ELK engine).

From the tool's definition "Compute layout for a model using ELK" and "Produces orthogonal edge routing" — triggers an external layout computation engine (ELK) that processes and transforms diagram data

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

POLICY

How to control layout_compute

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "layout_compute": {
      "limits": [
        {
          "counter": "layout_compute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

layout_compute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Engineering MCP Server tools

Destructive layout_delete Delete a layout from the store 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 →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Engineering MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about layout_compute

What does the layout_compute tool do? +

Compute layout for a model using ELK. Produces orthogonal edge routing suitable for P&ID diagrams. It is categorised as a Execute tool in the Engineering MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on layout_compute? +

Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for layout_compute: 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_compute? +

layout_compute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit layout_compute? +

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

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

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