get_server_public_key
AI agents call get_server_public_key to retrieve information from CV Recruitment Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Retrieving a public key is a read-only operation with no side effects. Public keys are meant to be distributed and do not change system state. The tool fits the Read category. Severity is low because exposure of a public key (by definition intended to be public) poses minimal direct risk.
From the tool's definition Tool name 'get_server_public_key' indicates retrieval of a public cryptographic key. The name contains the verb 'get', which is a read operation.
Attacks that exploit this kind of access
get_server_public_key. It is categorised as a Read tool in the CV Recruitment Assistant MCP Server, which means it retrieves data without modifying state.
Register the CV Recruitment Assistant MCP server in PolicyLayer and add a rule for get_server_public_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 CV Recruitment Assistant. Nothing to install.
get_server_public_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_server_public_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_server_public_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_server_public_key is provided by the CV Recruitment Assistant MCP server (noelserdna/cv-dinamic-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 →