AI agents call search_resumes_by_name 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 or queries resume documents by name without side effects. It fits the Read category: searches and retrieves data. Severity is low because the blast radius of misuse is limited to accessing personal career documents that the user already controls locally. No financial, destructive, or code execution implications.
From the tool's definition Tool name 'search_resumes_by_name' and server context indicate querying/searching local resume documents. Sibling tools are all 'get_*' operations (get_achievement, get_education, get_resume, etc.) that retrieve data.
Attacks that exploit this kind of access
search_resumes_by_name. 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 search_resumes_by_name: 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.
search_resumes_by_name 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 search_resumes_by_name 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 search_resumes_by_name. 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.
search_resumes_by_name 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 →