Retrieve the SSH public key for an app (used for manual deploy key setup)
AI agents call faber_get_deploy_key to retrieve information from Faber 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 an SSH public key, which is non-sensitive data intended for distribution and use in authentication workflows. It performs a query operation with no side effects, no data modification, and no execution of external operations. Public keys are designed to be public, so disclosure poses minimal risk. The tool falls clearly under the Read category.
From the tool's definition Tool name is 'faber_get_deploy_key' and description states 'Retrieve the SSH public key for an app'. The verb 'Retrieve' and the read-only nature of fetching a public key (which is meant to be shared) indicates no state modification.
Attacks that exploit this kind of access
Retrieve the SSH public key for an app (used for manual deploy key setup). It is categorised as a Read tool in the Faber MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Faber MCP Server MCP server in PolicyLayer and add a rule for faber_get_deploy_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 Faber MCP Server. Nothing to install.
faber_get_deploy_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 faber_get_deploy_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 faber_get_deploy_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.
faber_get_deploy_key is provided by the Faber MCP Server MCP server (joshtrebilco/faber-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 →