n8n_update_credential · n8n Management MCP Server MCP

WHAT IT DOES

What n8n_update_credential does on n8n Management MCP Server

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

WHY IT NEEDS A POLICY

Why n8n_update_credential needs a policy

This tool modifies existing credentials (authentication data, API keys, OAuth tokens) reversibly. It is a Write operation because changes can theoretically be reverted by updating again. However, the severity is high because compromised credential updates could immediately affect all workflows using that credential, potentially allowing unauthorized access to integrated services.

From the tool's definition Tool description states 'Update credential name or authentication data' and 'rotating API keys or changing OAuth tokens.' These are modifications to stored authentication secrets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_update_credential Rate-limited

n8n_update_credential 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": {
    "n8n_update_credential": {
      "limits": [
        {
          "counter": "n8n_update_credential_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 n8n Management MCP Server, so you can run agents against it safely.

FAQ

Questions about n8n_update_credential

What does the n8n_update_credential tool do? +

Update credential name or authentication data. Use this when rotating API keys or changing OAuth tokens. Workflows using this credential will use updated auth immediately. It is categorised as a Write tool in the n8n Management MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on n8n_update_credential? +

Register the n8n Management MCP Server MCP server in PolicyLayer and add a rule for n8n_update_credential: 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 n8n Management MCP Server. Nothing to install.

What risk level is n8n_update_credential? +

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

Can I rate-limit n8n_update_credential? +

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

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

n8n_update_credential is provided by the n8n Management MCP Server MCP server (node2flow-th/n8n-management-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.