Archive/delete an absence record in Sanka.
AI agents call delete_absence to permanently remove resources in Sanka MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes absence records, which are personnel/HR data. Deletion of records cannot be undone and represents a destructive operation. While 'archive' might suggest reversibility, the explicit mention of 'delete' and the HR context (absence records) make this a destructive action with high blast radius if misused (e.g., erasing employee leave history).
From the tool's definition Tool name explicitly states 'delete_absence' and description says 'Archive/delete an absence record' — the use of 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Archive/delete an absence record in Sanka. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for delete_absence: 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.
delete_absence is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_absence 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 delete_absence. 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.
delete_absence 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 →