rules_apply

THE RISK

High Risk

Why rules_apply needs a policy

This tool does more than read; it executes validation logic and optionally applies automatic corrections (writes/modifies data). Since it can auto-fix issues, it crosses into Execute/Write territory. The most severe applicable category is Execute because it triggers automated processing with side effects that depend on arguments (whether auto-fix is enabled).

From the tool's definition 'Apply validation rules' and 'Optionally auto-fix issues' — the tool actively runs validation logic against diagrams and can modify them automatically via auto-fix

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

POLICY

How to control rules_apply

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

policy.json

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

rules_apply 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 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 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 rules_apply

What does the rules_apply tool do? +

Apply validation rules and return structured issues for LLM processing. Optionally auto-fix issues. 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 rules_apply? +

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

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

Can I rate-limit rules_apply? +

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

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

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