Get employee details by ID or email
AI agents call get_employee to retrieve information from Corporate LXP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves employee information without creating, modifying, deleting, or executing any operations. It is a simple read-only query that returns existing data. The low severity reflects minimal blast radius—an agent misusing this tool could only access employee data it is already authorized to view, with no ability to modify systems or trigger external actions.
From the tool's definition Tool name 'get_employee' and description 'Get employee details by ID or email' indicate data retrieval with no modification or side effects. This is a straightforward query operation.
Attacks that exploit this kind of access
Get employee details by ID or email. It is categorised as a Read tool in the Corporate LXP MCP MCP Server, which means it retrieves data without modifying state.
Register the Corporate LXP MCP server in PolicyLayer and add a rule for get_employee: 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 Corporate LXP MCP. Nothing to install.
get_employee 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_employee 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_employee. 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_employee is provided by the Corporate LXP MCP server (karthikrajkumar/corporate_lxp_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 →