Get the publishable keys of the active project
AI agents call get-publishable-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 existing publishable keys from the active project. It is a query/get operation that only reads data without creating, modifying, deleting, or executing any actions. Publishable keys are non-secret credentials intended for public use, so exposure of the retrieval capability poses minimal risk compared to secret key retrieval or key creation/deletion operations.
From the tool's definition Tool name 'get-publishable-keys' and description 'Get the publishable keys of the active project' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the publishable 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-publishable-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-publishable-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-publishable-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-publishable-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-publishable-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 →