Search for experiences related to a specific skill
AI agents call search_by_skill to retrieve information from Rishi's Interactive Resume 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 information from a resume database based on skill parameters. It has no side effects, does not modify data, does not execute commands, and does not involve financial transactions. It is a straightforward read-only search operation, making it a low-severity 'Read' category tool.
From the tool's definition Tool name is 'search_by_skill' and description states it 'Search for experiences related to a specific skill'. This is a query/search operation that retrieves data from a resume without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Search for experiences related to a specific skill. It is categorised as a Read tool in the Rishi's Interactive Resume MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rishi's Interactive Resume MCP Server MCP server in PolicyLayer and add a rule for search_by_skill: 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 Rishi's Interactive Resume MCP Server. Nothing to install.
search_by_skill 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_by_skill 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_by_skill. 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_by_skill is provided by the Rishi's Interactive Resume MCP Server MCP server (rishia/rishi-resume-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 →