AI agents call list_connections to retrieve information from Nango without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing connection data without modifying, deleting, or executing operations. It has no capability to change state or trigger external actions. The low severity reflects minimal blast radius—exposing connection metadata to an unauthorized agent poses information disclosure risks but cannot directly cause data loss, financial impact, or destructive changes.
From the tool's definition Tool name 'list_connections' and description 'List Nango connections' indicate data retrieval only. The mention of 'tag filters such as end_user_id and organization_id' confirms this is a query operation with no side effects.
Attacks that exploit this kind of access
List Nango connections. Prefer tag filters such as end_user_id and organization_id. It is categorised as a Read tool in the Nango MCP Server, which means it retrieves data without modifying state.
Register the Nango 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 Nango. 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 Nango MCP server (levsky22/nango-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 →