create_standard_connect_session · Nango MCP: Risk & Policy

WHAT IT DOES

What create_standard_connect_session does on Nango

AI agents use create_standard_connect_session to create or update resources in Nango — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nango environment.

WHY IT NEEDS A POLICY

Why create_standard_connect_session needs a policy

This tool creates a new resource (a Connect session) which is a reversible write operation. While sessions are typically temporary, creating one establishes state that affects subsequent API interactions and user authentication flows. The 'standard' variant with tags suggests parameterized session configuration.

From the tool's definition Tool name 'create_standard_connect_session' and description 'Create a Connect session' indicate creation of a new session object. Connect sessions in Nango are authentication/connection flow orchestration artifacts that modify platform state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_standard_connect_session Rate-limited

create_standard_connect_session stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_standard_connect_session": {
      "limits": [
        {
          "counter": "create_standard_connect_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nango, so you can run agents against it safely.

FAQ

Questions about create_standard_connect_session

What does the create_standard_connect_session tool do? +

Create a Connect session with recommended Nango tags plus optional MCP convention tags. It is categorised as a Write tool in the Nango MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_standard_connect_session? +

Register the Nango MCP server in PolicyLayer and add a rule for create_standard_connect_session: 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.

What risk level is create_standard_connect_session? +

create_standard_connect_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_standard_connect_session? +

Yes. Add a rate_limit block to the create_standard_connect_session 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.

How do I block create_standard_connect_session completely? +

Set action: deny in the PolicyLayer policy for create_standard_connect_session. 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.

What MCP server provides create_standard_connect_session? +

create_standard_connect_session 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.