Get the shield publishable key of the active project
AI agents call get-shield-publishable-key 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 is a straightforward read operation that retrieves configuration data (a publishable key). Publishable keys are non-sensitive credentials by design and are meant to be shared. The operation has no side effects, does not execute code, modify data, delete anything, or commit financial transactions. The blast radius of misuse is minimal since publishable keys are not secret credentials.
From the tool's definition The tool retrieves a shield publishable key via 'Get' operation with no modification or deletion indicated. Description states it fetches ('Get') an existing value from the active project.
Attacks that exploit this kind of access
Get the shield publishable key 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-shield-publishable-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.
get-shield-publishable-key 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-shield-publishable-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 get-shield-publishable-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.
get-shield-publishable-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 →