[Consolidated into model_save] Export P&ID topology as machine-readable GraphML. See docs/FEATURE_PARITY_MATRIX.md for migration guide.
AI agents call dexpi_export_graphml 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.
Exporting/serializing data to a format like GraphML is fundamentally a read/retrieval operation — it reads the existing model and outputs it in a different format without modifying or deleting anything. The note '[Consolidated into model_save]' introduces slight ambiguity about whether a save/write side effect occurs, but the core described action is an export (read).
From the tool's definition Export P&ID topology as machine-readable GraphML
Documented attack patterns abuse exactly the kind of access dexpi_export_graphml 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_export_graphml:
{
"version": "1",
"default": "deny",
"tools": {
"dexpi_export_graphml": {}
}
}dexpi_export_graphml is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[Consolidated into model_save] Export P&ID topology as machine-readable GraphML. 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.
Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for dexpi_export_graphml: 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_export_graphml is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dexpi_export_graphml 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_export_graphml. 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_export_graphml 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.