AI agents use create_credential to create or update resources in N8n — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N8n environment.
Classified as Write rather than Read because it creates/persists new data (a credential) with reversible effects. Severity is high because credentials are sensitive security artifacts; misconfigured or malicious credentials could be leveraged to compromise connected services and steal data. However, it does not move money (Financial), execute arbitrary code (Execute), or permanently destroy data (Destructive).
From the tool's definition Tool creates a new credential object. Description states 'Create a new credential.' Credentials in n8n are authentication artifacts that store sensitive data like API keys, passwords, and tokens used to authenticate with external services.
Attacks that exploit this kind of access
Create a new credential. Use get_credential_schema to discover required fields first. It is categorised as a Write tool in the N8n MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N8n MCP server in PolicyLayer and add a rule for 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 N8n. Nothing to install.
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 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 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.
create_credential is provided by the N8n MCP server (siddharth0903/n8n-mcp). 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 →