New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_attendance_record

Archive/delete an employee attendance record in Sanka.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/delete-attendance-record.md

What delete_attendance_record does on Sanka MCP Server

AI agents call delete_attendance_record 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.

Why delete_attendance_record is rated Critical

The tool performs destructive operations on employee attendance records by deleting or archiving them. This is irreversibly destructive because attendance records are business-critical HR documentation that cannot be recovered once removed. Misuse could result in loss of compliance records, audit trails, and payroll documentation.

From the tool's definition Tool name contains 'delete' and description states 'Archive/delete an employee attendance record' - indicates irreversible removal of HR/personnel data.

Questions about delete_attendance_record

What does the delete_attendance_record tool do? +

Archive/delete an employee attendance 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.

How do I enforce a policy on delete_attendance_record? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for delete_attendance_record: 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.

What risk level is delete_attendance_record? +

delete_attendance_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_attendance_record? +

Yes. Add a rate_limit block to the delete_attendance_record 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.

How do I block delete_attendance_record completely? +

Set action: deny in the PolicyLayer policy for delete_attendance_record. 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.

What MCP server provides delete_attendance_record? +

delete_attendance_record 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.

More on Sanka MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.