Lists leave requests for the requested period and statuses.
AI agents call leave.list_requests to retrieve information from Tlc Portal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves existing leave request data filtered by period and status. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions.
From the tool's definition The tool name 'leave.list_requests' and description 'Lists leave requests for the requested period and statuses' indicate it retrieves or queries data about leave requests without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Lists leave requests for the requested period and statuses. It is categorised as a Read tool in the Tlc Portal MCP Server, which means it retrieves data without modifying state.
Register the Tlc Portal MCP server in PolicyLayer and add a rule for leave.list_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 Tlc Portal. Nothing to install.
leave.list_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 leave.list_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 leave.list_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.
leave.list_requests is provided by the Tlc Portal MCP server (mingovvv/tlc-portal-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 →