AI agents call describe_connection_convention 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 a read-only operation—it describes or explains existing connection convention helpers without modifying, executing, or deleting any data. It is purely informational in nature, making it a Read category tool with low severity since misuse would only return documentation without side effects.
From the tool's definition Tool name 'describe_connection_convention' and description 'Explain the optional Nango MCP connection convention helpers' indicate this is a documentation/explanation tool that retrieves and presents information about connection conventions.
Attacks that exploit this kind of access
Explain the optional Nango MCP connection convention helpers. 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 describe_connection_convention: 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.
describe_connection_convention 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 describe_connection_convention 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 describe_connection_convention. 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.
describe_connection_convention 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 →