AI agents call get_pipeline to retrieve information from ParaView-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves metadata about the current state of the ParaView visualization pipeline. It has no capacity to create, modify, delete, or execute changes to data or visualizations. The blast radius of misuse is minimal—an AI agent cannot cause damage by reading pipeline structure information.
From the tool's definition The tool name 'get_pipeline' combined with the description 'Get the current pipeline structure' indicates a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_pipeline 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 get_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"get_pipeline": {}
}
}get_pipeline is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current pipeline structure. It is categorised as a Read tool in the ParaView-MCP MCP Server, which means it retrieves data without modifying state.
Register the ParaView- MCP server in PolicyLayer and add a rule for get_pipeline: 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.
get_pipeline is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pipeline 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 get_pipeline. 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.
get_pipeline 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.