create-connection
AI agents use create-connection to create or update resources in Workato MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Workato MCP Server environment.
Creating a connection in Workato involves establishing a credential or API integration link, which modifies the system state by adding a new connection resource. This is a reversible Write operation—connections can be deleted or modified later. While the description is empty, the context from sibling tools and the 'create-' prefix strongly indicates a Write category.
From the tool's definition Tool name 'create-connection' indicates creation of a connection resource. Sibling tools on the Workato MCP Server include 'create-folder', 'create-recipe', and 'create-tag', which are clearly Write operations.
Attacks that exploit this kind of access
create-connection. It is categorised as a Write tool in the Workato MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Workato MCP Server MCP server in PolicyLayer and add a rule for create-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 Workato MCP Server. Nothing to install.
create-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 create-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 create-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.
create-connection is provided by the Workato MCP Server MCP server (jacobgoren-sb/workato-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 →