AI agents call search_resumes_by_skills 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 searches and retrieves resume documents filtered by skills criteria. It retrieves data with no side effects—no creation, modification, deletion, code execution, or financial operations. Despite the empty description, the naming convention, server purpose, and sibling tools collectively provide high confidence this is a simple search/query operation.
From the tool's definition Tool name 'search_resumes_by_skills' indicates querying/searching functionality. Server description confirms it's for 'browsing and searching your local resume and job application documents'. All sibling tools are retrieval-only (get_*, list_*).
Attacks that exploit this kind of access
search_resumes_by_skills. 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_skills: 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_skills 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_skills 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_skills. 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_skills 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 →