n8n_manage_credentials · n8n- MCP: Risk & Policy

WHAT IT DOES

What n8n_manage_credentials does on n8n-MCP

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

WHY IT NEEDS A POLICY

Why n8n_manage_credentials needs a policy

While the tool includes destructive (delete) and read (list, get) capabilities, the primary risk is at the Write level. Credentials management allows creating and modifying authentication tokens and secrets that control access to external systems. The delete action could be destructive in isolation, but the tool's core function centers on reversible credential lifecycle management (create, update).

From the tool's definition Tool supports create, update, delete, and list operations on credentials. Description explicitly states 'Manage n8n credentials' with actions including create, update, delete.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_manage_credentials Rate-limited

n8n_manage_credentials 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_manage_credentials": {
      "limits": [
        {
          "counter": "n8n_manage_credentials_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-MCP, so you can run agents against it safely.

FAQ

Questions about n8n_manage_credentials

What does the n8n_manage_credentials tool do? +

Manage n8n credentials. Actions: list, get, create, update, delete, getSchema. Use getSchema to discover required fields before creating. SECURITY: credential data values are never logged. It is categorised as a Write tool in the n8n-MCP 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_manage_credentials? +

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

What risk level is n8n_manage_credentials? +

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

Can I rate-limit n8n_manage_credentials? +

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

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

n8n_manage_credentials is provided by the n8n- MCP server (spring1237/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.