AI agents use toggle_visibility 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.
Toggling visibility modifies the state of visualization objects within ParaView (reversible state change), but does not delete data or execute arbitrary code. This is a Write operation with medium severity because an agent could hide critical visualization layers, potentially disrupting analysis workflows or obscuring important scientific data, though changes are easily reversible.
From the tool's definition Tool name 'toggle_visibility' combined with sibling tools that create and manipulate visualizations (create_isosurface, create_slice, create_streamline, edit_volume_opacity) indicates this toggles the display state of visualization objects in ParaView's scene.
Documented attack patterns abuse exactly the kind of access toggle_visibility 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 toggle_visibility:
{
"version": "1",
"default": "deny",
"tools": {
"toggle_visibility": {
"limits": [
{
"counter": "toggle_visibility_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}toggle_visibility 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.
toggle_visibility. 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 toggle_visibility: 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.
toggle_visibility 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 toggle_visibility 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 toggle_visibility. 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.
toggle_visibility 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.