plot_scatter
AI agents use plot_scatter 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.
Based on the server context and sibling tools (plot_bar, plot_box, plot_line, etc.), plot_scatter almost certainly generates a scatter plot visualization and writes/saves an output file. This is a Write operation (creating a figure artifact). The empty description lowers confidence, but the pattern is highly consistent with the other plotting tools on this server.
From the tool's definition Tool name 'plot_scatter' on a server described as providing tools for 'creating publication-quality scientific visualizations, statistical plots, and 2D data representations'; description is empty.
Attacks that exploit this kind of access
plot_scatter. 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_scatter: 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_scatter 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_scatter 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_scatter. 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_scatter 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 →