Generate a symmetric or asymmetric key.
AI agents use generate_key to create or update resources in Pangea MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pangea MCP Server environment.
Generating cryptographic keys is a Write operation because it creates new data artifacts that are stored and can be used subsequently. It is reversible (keys can be deleted via delete_vault_item).
From the tool's definition Tool name is 'generate_key' and description states it can 'Generate a symmetric or asymmetric key.' This creates new cryptographic material that is stored (likely in the Vault service based on server context).
Attacks that exploit this kind of access
Generate a symmetric or asymmetric key. It is categorised as a Write tool in the Pangea MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pangea MCP Server MCP server in PolicyLayer and add a rule for generate_key: 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 Pangea MCP Server. Nothing to install.
generate_key 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 generate_key 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 generate_key. 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.
generate_key is provided by the Pangea MCP Server MCP server (pangeacyber/pangea-mcp-server). 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 →