AI agents call check_environment 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 is a read-only operation that queries and returns environment configuration metadata. The explicit exclusion of secret keys indicates security awareness and limits exposure. The operation has no side effects and cannot alter system state. Severity is low because the information returned is non-sensitive configuration data that would not enable further attacks without additional context.
From the tool's definition Tool name is 'check_environment' and description states it 'Resolve one configured Nango environment without returning its secret key.' The action is purely informational—it retrieves environment configuration details but explicitly excludes sensitive secrets.
Attacks that exploit this kind of access
Resolve one configured Nango environment without returning its secret key. 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 check_environment: 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.
check_environment 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 check_environment 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 check_environment. 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.
check_environment 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 →