Save the currently active contour (or any surface/mesh source) as an STL file
AI agents use save_contour_as_stl to create or update resources in ParaView-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ParaView-MCP environment.
The tool creates a new file (STL export) which is a reversible write operation — the file can be deleted or overwritten later. It does not delete existing data, execute arbitrary code, or move financial resources. While file creation has some side effects, it is not destructive (the original visualization remains intact).
From the tool's definition Tool description states "Save the currently active contour (or any surface/mesh source) as an STL file" — this creates/writes a new file to disk.
Documented attack patterns abuse exactly the kind of access save_contour_as_stl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ParaView-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for save_contour_as_stl:
{
"version": "1",
"default": "deny",
"tools": {
"save_contour_as_stl": {
"limits": [
{
"counter": "save_contour_as_stl_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_contour_as_stl 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.
Save the currently active contour (or any surface/mesh source) as an STL file. It is categorised as a Write tool in the ParaView-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ParaView- MCP server in PolicyLayer and add a rule for save_contour_as_stl: 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 ParaView-MCP. Nothing to install.
save_contour_as_stl 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 save_contour_as_stl 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 save_contour_as_stl. 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.
save_contour_as_stl is provided by the ParaView- MCP server (llnl/paraview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ParaView-MCP, 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.
23 ParaView-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.