Low Risk

dexpi_export_json

[Consolidated into model_save] Export P&ID model as JSON. See docs/FEATURE_PARITY_MATRIX.md for migration guide.

How to control dexpi_export_json ↓

What dexpi_export_json does on Engineering MCP Server

AI agents call dexpi_export_json to retrieve information from Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why dexpi_export_json needs a policy

Exporting/serializing a model to JSON is a read operation — it retrieves and formats existing data without modifying or deleting anything. The note '[Consolidated into model_save]' introduces slight ambiguity about whether saving is involved, but the described action is an export/read. Confidence is reduced because the description is sparse and references a deprecated/consolidated state.

From the tool's definition Export P&ID model as JSON

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

How to control dexpi_export_json

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dexpi_export_json": {}
  }
}

dexpi_export_json is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Engineering MCP Server — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about dexpi_export_json

What does the dexpi_export_json tool do? +

[Consolidated into model_save] Export P&ID model as JSON. See docs/FEATURE_PARITY_MATRIX.md for migration guide. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dexpi_export_json? +

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

dexpi_export_json is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dexpi_export_json? +

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

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

dexpi_export_json 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.

Free to start. No card required.

72 Engineering MCP Server 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.