Create a new connection with name, type, and configuration
AI agents use alfred_create_connection to create or update resources in Alfred MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alfred MCP Server environment.
This tool creates a new connection resource with configuration data, which is a reversible write operation. While connections may enable downstream access to external systems, the creation itself does not execute commands, delete data, or move money.
From the tool's definition Tool description states 'Create a new connection' — a reversible data creation operation. The sibling tools include destructive operations (delete_*) and execution tools, confirming this is in the Write category.
Attacks that exploit this kind of access
Create a new connection with name, type, and configuration. It is categorised as a Write tool in the Alfred MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alfred MCP Server MCP server in PolicyLayer and add a rule for alfred_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 Alfred MCP Server. Nothing to install.
alfred_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 alfred_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 alfred_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.
alfred_create_connection is provided by the Alfred MCP Server MCP server (lumberjack-so/alfred-mcp). 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 →