plot_graph
AI agents invoke plot_graph to trigger actions in Vibe Preprocessing and Analysis MCP Server. 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.
The tool name 'plot_graph' suggests generating visualizations, which likely involves executing rendering code. The empty description lowers confidence, but sibling tools like 'run_custom_graph_code' and 'run_custom_df_edit_code' indicate this server executes code. Plotting a graph could involve executing arbitrary code depending on implementation.
From the tool's definition Tool name 'plot_graph' on a server with sibling tool 'run_custom_graph_code' that likely executes code for graph generation; server description mentions 'graph generation'.
Attacks that exploit this kind of access
plot_graph. It is categorised as a Execute tool in the Vibe Preprocessing and Analysis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vibe Preprocessing and Analysis MCP Server MCP server in PolicyLayer and add a rule for plot_graph: 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 Vibe Preprocessing and Analysis MCP Server. Nothing to install.
plot_graph 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_graph 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_graph. 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_graph is provided by the Vibe Preprocessing and Analysis MCP Server MCP server (mudit14224/vibe-data-analysis). 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 →