Create a new wafle API key with the given scopes. Returns the secret ONCE — store it immediately.\n\n
AI agents use wafle_auth_keys_create to create or update resources in wafle MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your wafle MCP server environment.
This tool creates new API keys, which are credentials that grant access to the wafle platform. While creation is technically reversible (keys can be revoked), the act of generating and exposing a secret token is a Write operation that establishes new authentication pathways. This is Write rather than Destructive because key revocation is a standard, reversible operation.
From the tool's definition Tool name 'wafle_auth_keys_create' and description 'Create a new wafle API key' indicates irreversible creation of authentication credentials. The note 'Returns the secret ONCE — store it immediately' confirms this creates persistent security artifacts.
Attacks that exploit this kind of access
Create a new wafle API key with the given scopes. Returns the secret ONCE — store it immediately.\n\n. It is categorised as a Write tool in the wafle MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_auth_keys_create: 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 wafle MCP server. Nothing to install.
wafle_auth_keys_create 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 wafle_auth_keys_create 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 wafle_auth_keys_create. 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.
wafle_auth_keys_create is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →