Create a data connection. MQTT: connects to a broker and subscribes to topics. WebSocket: connects to a remote WS URL. Webhook: creates an HTTP ingest endpoint.
AI agents use create_connection to create or update resources in LiveTap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LiveTap environment.
The tool creates new data ingestion configurations that are stored and managed by the system. While not destructive or financially impactful, it modifies system state by adding new connections that could channel external data streams into the agent's context. A misused connection could be used to ingest malicious or sensitive data streams, or to establish unwanted connections to external services.
From the tool's definition Tool description states it 'Create[s] a data connection' and establishes connections to external systems (MQTT brokers, WebSocket URLs, HTTP webhooks). This is a write operation that creates and persists new connection configurations.
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 LiveTap, 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 data connection. MQTT: connects to a broker and subscribes to topics. WebSocket: connects to a remote WS URL. Webhook: creates an HTTP ingest endpoint. It is categorised as a Write tool in the LiveTap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LiveTap 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 LiveTap. 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 LiveTap MCP server (livetap/livetap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LiveTap, 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.
13 LiveTap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.