render_flow_visualization
Render flow visualization with colored bounding boxes for each flow group. Supports overlay on a rendered page image or synthetic dark canvas fallback. Handles wide Figma pages (>3:1 aspect ratio) and uses cross-platform fonts (Windows/macOS/Linux with PIL default fallback).
This record as markdown: /tools/io-github-homenshum-nodebench/render-flow-visualization.md
What render_flow_visualization does on Nodebench
AI agents invoke render_flow_visualization to trigger actions in Nodebench. 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.
Why render_flow_visualization is rated High
This tool renders/generates visual output by processing page images and drawing overlays, which constitutes execution of image processing operations with external dependencies (PIL, font rendering, page rendering). It produces output files/images rather than simply reading data, and involves triggering rendering pipelines.
From the tool's definition Render flow visualization with colored bounding boxes for each flow group. Supports overlay on a rendered page image or synthetic dark canvas fallback.
Attacks that exploit this kind of access
The rule that runs render_flow_visualization safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_flow_visualization, this is the rule to start with:
render_flow_visualization stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every render_flow_visualization call is checked against it from then on.
Questions about render_flow_visualization
Render flow visualization with colored bounding boxes for each flow group. Supports overlay on a rendered page image or synthetic dark canvas fallback. Handles wide Figma pages (>3:1 aspect ratio) and uses cross-platform fonts (Windows/macOS/Linux with PIL default fallback). It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodebench MCP server in PolicyLayer and add a rule for render_flow_visualization: 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 Nodebench. Nothing to install.
render_flow_visualization 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 render_flow_visualization 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 render_flow_visualization. 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.
render_flow_visualization is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue