Get leave history for the employee
AI agents call get_leave_history to retrieve information from Sequential Thinking MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation that queries employee leave records. It has no capability to modify, delete, or execute actions. The blast radius is minimal since it only exposes read-only access to historical records, typically considered low-sensitivity HR data that may already be accessible to the employee themselves or HR personnel.
From the tool's definition Tool name is 'get_leave_history' and description states 'Get leave history for the employee' — purely retrieves historical leave data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get leave history for the employee. It is categorised as a Read tool in the Sequential Thinking MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sequential Thinking MCP Server 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 Sequential Thinking MCP Server. 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 Sequential Thinking MCP Server MCP server (younis-ali/sequential-thinking-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 →