update_integration · Nango MCP: Risk & Policy

WHAT IT DOES

What update_integration does on Nango

AI agents use update_integration 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 update_integration needs a policy

This tool creates or modifies integration data within the Nango platform. Updates to integrations can affect authentication flows, API credentials, and connection behavior for multiple dependent systems, creating moderate blast radius if misconfigured.

From the tool's definition Tool name 'update_integration' with description 'Patch a Nango integration' indicates modification of existing integration configuration data. The verb 'patch' confirms reversible update semantics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_integration Rate-limited

update_integration 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": {
    "update_integration": {
      "limits": [
        {
          "counter": "update_integration_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 update_integration

What does the update_integration tool do? +

Patch a Nango integration. 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 update_integration? +

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

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

Can I rate-limit update_integration? +

Yes. Add a rate_limit block to the update_integration 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 update_integration completely? +

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

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