[Consolidated into model_save] Export flowsheet topology as GraphML. See docs/FEATURE_PARITY_MATRIX.md for migration guide.
AI agents use sfiles_export_graphml 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.
This tool performs an export operation—writing/serializing engineering diagram data to GraphML format. While export itself is read-like in intent, the consolidation into 'model_save' and the context of persisting process-engineering diagrams across the server suggest this creates or outputs data artifacts. Export operations that produce new files or serialized outputs are classified as Write rather than Read.
From the tool's definition Tool exports flowsheet topology as GraphML, which is a data serialization/export operation that creates or produces output data. The description indicates it is now consolidated into 'model_save', suggesting it persists or exports diagram data.
Documented attack patterns abuse exactly the kind of access sfiles_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 sfiles_export_graphml:
{
"version": "1",
"default": "deny",
"tools": {
"sfiles_export_graphml": {
"limits": [
{
"counter": "sfiles_export_graphml_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sfiles_export_graphml 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_save] Export flowsheet topology as GraphML. 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 sfiles_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.
sfiles_export_graphml 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 sfiles_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 sfiles_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.
sfiles_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.