[Consolidated into model_load] Import P&ID model from JSON. See docs/FEATURE_PARITY_MATRIX.md for migration guide.
AI agents use dexpi_import_json to create or update resources in Engineering MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Engineering MCP Server environment.
Import operations read external data and write/load it into the application state, making this a Write action rather than pure Read. The severity is medium because while the operation modifies diagrams, it is reversible (can be undone or overwritten) and the blast radius is limited to engineering diagram data rather than system-critical or financial operations.
From the tool's definition Tool name 'dexpi_import_json' and description 'Import P&ID model from JSON' indicates the tool loads/ingests external JSON data into the system, modifying the in-memory or persisted P&ID model state.
Documented attack patterns abuse exactly the kind of access dexpi_import_json gives an agent:
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_import_json:
{
"version": "1",
"default": "deny",
"tools": {
"dexpi_import_json": {
"limits": [
{
"counter": "dexpi_import_json_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dexpi_import_json stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[Consolidated into model_load] Import P&ID model from JSON. See docs/FEATURE_PARITY_MATRIX.md for migration guide. It is categorised as a Write tool in the Engineering MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for dexpi_import_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.
dexpi_import_json is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dexpi_import_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.
Set action: deny in the PolicyLayer policy for dexpi_import_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.
dexpi_import_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.
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.