AI agents invoke plot_over_line to trigger actions in ParaView-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Given the ParaView context and sibling tools that create visualization objects (create_isosurface, create_slice, create_streamline), plot_over_line likely executes a ParaView pipeline operation to sample and plot data along a line. This is an Execute-level action as it triggers an external operation in ParaView. Confidence is low due to empty description.
From the tool's definition Tool name 'plot_over_line' with empty description. Based on sibling tools context (ParaView scientific visualization server with tools like create_isosurface, create_slice, create_streamline), this tool likely creates a plot-over-line filter/operation in…
Documented attack patterns abuse exactly the kind of access plot_over_line 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 plot_over_line:
{
"version": "1",
"default": "deny",
"tools": {
"plot_over_line": {
"limits": [
{
"counter": "plot_over_line_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}plot_over_line stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
plot_over_line. It is categorised as a Execute tool in the ParaView-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ParaView- MCP server in PolicyLayer and add a rule for plot_over_line: 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.
plot_over_line is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the plot_over_line 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 plot_over_line. 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.
plot_over_line 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.