AI agents use create_connection to create or update resources in Automatisch MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automatisch MCP Server environment.
Creating a connection establishes a new integration with an external service, potentially storing credentials or API keys. While reversible (can be deleted), this is a Write operation that creates persistent state. Severity is high because a malicious agent could create connections to unauthorized services, exfiltrate data through created connections, or establish persistence mechanisms.
From the tool's definition Tool description states 'Create a new app connection' which is a reversible data creation operation. Context indicates this is part of a workflow automation platform where connections link to external apps and services.
Documented attack patterns abuse exactly the kind of access create_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automatisch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_connection:
{
"version": "1",
"default": "deny",
"tools": {
"create_connection": {
"limits": [
{
"counter": "create_connection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create a new app connection. It is categorised as a Write tool in the Automatisch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automatisch 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 Automatisch 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 Automatisch MCP Server MCP server (milisp/automatisch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automatisch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Automatisch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.