AI agents call get-flows to retrieve information from Node Red without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves flow data from Node-RED without modification. The 'get-' prefix is a standard convention for read-only operations. Even though the description is empty, the context of sibling tools and naming patterns indicate this is a simple data retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get-flows' indicates data retrieval. Sibling tools show a clear pattern where 'get-*' tools are read operations (get-diagnostics, get-flow, get-flows-formatted, get-flows-state, get-node-info, get-nodes), while 'create-*' and 'delete-*' are…
Attacks that exploit this kind of access
get-flows. It is categorised as a Read tool in the Node Red MCP Server, which means it retrieves data without modifying state.
Register the Node Red MCP server in PolicyLayer and add a rule for get-flows: 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 Node Red. Nothing to install.
get-flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-flows 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 get-flows. 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.
get-flows is provided by the Node Red MCP server (node-red-mcp-server). 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 →