get_leave_requests
AI agents call get_leave_requests to retrieve information from Attendance Management 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 leave request data without modifying state. The 'get_' prefix and context among sibling read-only query tools (get_attendance_records, get_employee_schedule, etc.) strongly indicate data retrieval. No side effects or data manipulation implied. Blast radius is minimal—an AI agent querying leave requests poses no operational or financial risk.
From the tool's definition Tool name 'get_leave_requests' follows read-pattern naming convention (get_*). Server description mentions 'querying attendance information' and 'managing employee leave requests', contextualizing this as a retrieval operation.
Attacks that exploit this kind of access
get_leave_requests. It is categorised as a Read tool in the Attendance Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Attendance Management MCP Server MCP server in PolicyLayer and add a rule for get_leave_requests: 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 Attendance Management MCP Server. Nothing to install.
get_leave_requests 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_requests 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_requests. 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_requests is provided by the Attendance Management MCP Server MCP server (shineliang/att-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 →