Plot funding trends over years by city.
AI agents invoke plot_funding_trend to trigger actions in VayuChat 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.
This tool executes Python code with matplotlib to generate visualizations. While it is primarily a read/display operation, it involves code execution in the server environment to produce charts. It does not write persistent data or perform destructive actions, but misuse could trigger resource-intensive computations.
From the tool's definition 'Plot funding trends over years by city' — generates a matplotlib visualization, which involves executing Python/pandas code to process data and render output
Attacks that exploit this kind of access
Plot funding trends over years by city. It is categorised as a Execute tool in the VayuChat MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VayuChat MCP server in PolicyLayer and add a rule for plot_funding_trend: 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 VayuChat MCP. Nothing to install.
plot_funding_trend 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_funding_trend 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_funding_trend. 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_funding_trend is provided by the VayuChat MCP server (nipunbatra/vayuchat-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 →