AI agents use set_color_map 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 modifies ParaView visualization rendering (color mapping), which changes the display state of scientific visualizations. This is a reversible write operation—color maps can be changed back or reset. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).
From the tool's definition Tool name 'set_color_map' indicates modification of visualization properties; sibling tools like 'color_by', 'edit_volume_opacity', and other creation/modification tools confirm this server manipulates ParaView visualization state.
Documented attack patterns abuse exactly the kind of access set_color_map 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 set_color_map:
{
"version": "1",
"default": "deny",
"tools": {
"set_color_map": {
"limits": [
{
"counter": "set_color_map_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_color_map 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.
set_color_map. 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 set_color_map: 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.
set_color_map 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 set_color_map 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 set_color_map. 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.
set_color_map 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.