AI agents call audit_connection_conventions 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 performs an audit—a review and analysis function—to suggest conventions for metadata/tags on existing connections. It retrieves information about connection configurations and provides recommendations, but does not modify, delete, or execute external operations. The blast radius of misuse is minimal; providing incorrect audit suggestions has no direct side effects on systems or data integrity.
From the tool's definition Tool name 'audit_connection_conventions' with description 'Audit Nango connections for suggested MCP tag/metadata conventions' indicates inspection and analysis of existing configuration without modification.
Attacks that exploit this kind of access
Audit Nango connections for suggested MCP tag/metadata conventions. 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 audit_connection_conventions: 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.
audit_connection_conventions 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 audit_connection_conventions 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 audit_connection_conventions. 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.
audit_connection_conventions 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 →