AI agents use create_slice 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.
Based on the tool name and the context of sibling tools (create_isosurface, create_source, create_streamline), this tool likely creates a new slice visualization object in the ParaView pipeline. This is a Write operation as it creates a new visualization element. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'create_slice' suggests creation of a new slice object in the ParaView pipeline. Description is empty, providing no additional information.
Documented attack patterns abuse exactly the kind of access create_slice 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 create_slice:
{
"version": "1",
"default": "deny",
"tools": {
"create_slice": {
"limits": [
{
"counter": "create_slice_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_slice 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.
create_slice. 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 create_slice: 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.
create_slice 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 create_slice 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 create_slice. 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.
create_slice 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.