AI agents call get_resume to retrieve information from Resume without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns resume document content. The operation is read-only with no capability to modify, delete, or execute external operations. The data retrieved is the user's own local resume document.
From the tool's definition Tool name 'get_resume' and description 'Return the full extracted text of a document' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Return the full extracted text of a document. It is categorised as a Read tool in the Resume MCP Server, which means it retrieves data without modifying state.
Register the Resume MCP server in PolicyLayer and add a rule for get_resume: 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 Resume. Nothing to install.
get_resume 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_resume 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_resume. 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_resume is provided by the Resume MCP server (mnoomnoo/resume-mcp-server). 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 →