add_connection
Create a connection between two nodes in a workflow. Connects an output socket to an input socket.
This record as markdown: /tools/flowdot-llc-mcp-server/add-connection.md
What add_connection does on FlowDot MCP Server
AI agents use add_connection to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why add_connection is rated Medium
This tool creates new workflow connections, which modifies the workflow structure reversibly. It is a Write operation because connections can be created and subsequently removed or modified without permanent data loss. The severity is medium because misuse could disrupt workflow logic and automation chains, but the effect is limited to workflow structure rather than data deletion or external system impact.
From the tool's definition Tool description states 'Create a connection between two nodes in a workflow. Connects an output socket to an input socket.' The verb 'Create' and action of establishing connections indicates data modification.
Attacks that exploit this kind of access
The rule that runs add_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_connection, this is the rule to start with:
add_connection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every add_connection call is checked against it from then on.
Questions about add_connection
Create a connection between two nodes in a workflow. Connects an output socket to an input socket. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for add_connection: 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 FlowDot MCP Server. Nothing to install.
add_connection 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 add_connection 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 add_connection. 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.
add_connection is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue