Get leave history for the employee
AI agents call get_leave_history to retrieve information from Leave Management without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays leave history data without modifying, deleting, or executing any operations. It has minimal blast radius if misused by an AI agent—at worst, an employee could view leave history they already have legitimate access to. No financial, destructive, or execution-based consequences possible.
From the tool's definition Tool name 'get_leave_history' and description 'Get leave history for the employee' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of accessing historical records confirm this is a query operation.
Attacks that exploit this kind of access
Get leave history for the employee. It is categorised as a Read tool in the Leave Management MCP Server, which means it retrieves data without modifying state.
Register the Leave Management MCP server in PolicyLayer and add a rule for get_leave_history: 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 Leave Management. Nothing to install.
get_leave_history 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_leave_history 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_leave_history. 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_leave_history is provided by the Leave Management MCP server (kanthirayakota-cloud/mcp1_leave_manager). 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 →