AI agents use n8n_create_credential to create or update resources in Mcp N8n — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp N8n environment.
This tool creates new credentials in n8n, which are sensitive authentication artifacts used to access external systems and services. While creation itself is reversible (Write rather than Destructive), credentials are critical security-sensitive objects. Misuse could allow an AI agent to create credentials for unauthorized access to external systems, compromise integrations, or enable lateral movement.
From the tool's definition Tool name is 'n8n_create_credential' and description states 'Create a new credential.' The verb 'create' indicates data creation/modification rather than retrieval or destruction.
Attacks that exploit this kind of access
Create a new credential. It is categorised as a Write tool in the Mcp N8n MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp N8n MCP server in PolicyLayer and add a rule for n8n_create_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 Mcp N8n. Nothing to install.
n8n_create_credential is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the n8n_create_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.
Set action: deny in the PolicyLayer policy for n8n_create_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.
n8n_create_credential is provided by the Mcp N8n MCP server (lyzetam/mcp-n8n). 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 →