List all active connections with their status, message rate, and buffered count.
AI agents call list_connections to retrieve information from LiveTap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing connections without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves metadata about active connections. The low severity reflects minimal risk even if misused by an agent, as it only exposes system state information.
From the tool's definition Tool name is 'list_connections' and description states it 'List[s] all active connections with their status, message rate, and buffered count' — a pure retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_connections 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 list_connections:
{
"version": "1",
"default": "deny",
"tools": {
"list_connections": {}
}
}list_connections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active connections with their status, message rate, and buffered count. It is categorised as a Read tool in the LiveTap MCP Server, which means it retrieves data without modifying state.
Register the LiveTap MCP server in PolicyLayer and add a rule for list_connections: 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.
list_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_connections 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 list_connections. 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.
list_connections 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.