plot_bar
AI agents use plot_bar to create or update resources in ML Research MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ML Research MCP environment.
The description is empty, so classification relies on the tool name and server context. 'plot_bar' is consistent with the sibling tools (plot_box, plot_histogram, plot_scatter, etc.), all of which generate visualization files/outputs. This constitutes a Write action — creating a new artifact (a bar chart file or rendered figure) — with no indication of destructive, financial, or execution behavior.
From the tool's definition Tool name 'plot_bar' on a server described as providing tools for 'creating publication-quality scientific visualizations, statistical plots, and 2D data representations'
Attacks that exploit this kind of access
plot_bar. It is categorised as a Write tool in the ML Research MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ML Research MCP server in PolicyLayer and add a rule for plot_bar: 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 ML Research MCP. Nothing to install.
plot_bar 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 plot_bar 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_bar. 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_bar is provided by the ML Research MCP server (nishide-dev/ml-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →