Get the secret keys of the active project
AI agents call get-secret-keys to retrieve information from Openfort MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive cryptographic credentials (secret keys) from the active project. While the action itself is a read operation (no data is modified or deleted), the severity is high because exposure of secret keys could allow unauthorized access to wallet infrastructure and financial transactions. However, the category is Read because the tool only retrieves existing data without modifying it.
From the tool's definition Tool name 'get-secret-keys' and description 'Get the secret keys of the active project' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the secret keys of the active project. It is categorised as a Read tool in the Openfort MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Openfort MCP Server MCP server in PolicyLayer and add a rule for get-secret-keys: 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.
get-secret-keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-secret-keys 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 get-secret-keys. 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.
get-secret-keys 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 →