Review leave and absence records in Sanka. Use this for vacation, PTO, sick leave, and other absence requests.
AI agents call list_absences to retrieve information from Sanka 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 and queries existing absence/leave records without creating, modifying, deleting, or executing any operations. It has minimal blast radius as misuse would only expose information about existing absences, not cause data changes or financial impact.
From the tool's definition Tool name 'list_absences' and description 'Review leave and absence records' indicates a retrieval operation with no side effects. The verb 'Review' and action of querying absence records confirms read-only behavior.
Attacks that exploit this kind of access
Review leave and absence records in Sanka. Use this for vacation, PTO, sick leave, and other absence requests. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_absences: 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 Sanka MCP Server. Nothing to install.
list_absences 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 list_absences 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 list_absences. 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.
list_absences is provided by the Sanka MCP Server MCP server (sankahq/sanka-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 →