AI agents use resize_nodes to create or update resources in AI Charts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI Charts environment.
This tool creates or modifies diagram element properties in a reversible manner. Resizing is a standard diagram editing operation that can be undone (either by resizing again or resetting to auto-size via null). It does not delete, execute commands, move money, or trigger external operations—it simply adjusts visual presentation attributes of existing diagram nodes. This fits the Write category.
From the tool's definition Tool description: 'Resize one or more nodes. Pass null for width/height to reset to auto-size.' The action modifies diagram node properties (width/height dimensions) reversibly without deleting data or executing external code.
Attacks that exploit this kind of access
Resize one or more nodes. Pass null for width/height to reset to auto-size. It is categorised as a Write tool in the AI Charts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI Charts MCP server in PolicyLayer and add a rule for resize_nodes: 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 AI Charts. Nothing to install.
resize_nodes 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 resize_nodes 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 resize_nodes. 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.
resize_nodes is provided by the AI Charts MCP server (tjameswilliams/ai-charts). 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 →