Create a new secret key for the active project and return all the existing ones
AI agents use create-secret-key to create or update resources in Openfort MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openfort MCP Server environment.
This tool creates and returns secret keys, which are sensitive cryptographic material used for authentication and authorization. While creation itself is reversible (keys can be revoked), secret keys are high-value targets for attackers and their generation without proper controls could lead to unauthorized access.
From the tool's definition Tool name 'create-secret-key' and description 'Create a new secret key for the active project' explicitly indicate creation of cryptographic credentials.
Attacks that exploit this kind of access
Create a new secret key for the active project and return all the existing ones. It is categorised as a Write tool in the Openfort MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openfort MCP Server MCP server in PolicyLayer and add a rule for create-secret-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 Openfort MCP Server. Nothing to install.
create-secret-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 create-secret-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 create-secret-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.
create-secret-key is provided by the Openfort MCP Server MCP server (openfort-xyz/-deprecated-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 →