AI agents call list_integrations 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 queries and returns a list of existing integrations. It has no side effects, does not modify data, and does not execute external operations or code. It is a straightforward data retrieval operation, making it a Read category risk with low severity since unauthorized access to configuration lists has limited blast radius compared to write or destructive operations.
From the tool's definition Tool name is 'list_integrations' and description states it 'List integrations configured in one Nango environment.' The verb 'list' is a read-only operation that retrieves information without modifying data.
Attacks that exploit this kind of access
List integrations configured in one Nango environment. 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_integrations: 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_integrations 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_integrations 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_integrations. 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_integrations 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 →