Get detailed information about experience at a specific company
AI agents call get_company_details 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 queries resume data without side effects. It returns information about past employment at a specific company. There is no capability to modify, delete, execute code, trigger external operations, or commit financial transactions.
From the tool's definition Tool name is 'get_company_details' and description states it retrieves 'detailed information about experience at a specific company' — purely a data retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get detailed information about experience at a specific company. 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 get_company_details: 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.
get_company_details 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_company_details 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_company_details. 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_company_details 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 →