update_attendance_record · Sanka MCP Server MCP

WHAT IT DOES

What update_attendance_record does on Sanka MCP Server

AI agents use update_attendance_record to create or update resources in Sanka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

WHY IT NEEDS A POLICY

Why update_attendance_record needs a policy

This tool modifies employee attendance and time tracking records, which are business-critical data affecting payroll, compliance, and employee compensation. While the change is reversible (Write category, not Destructive), the high severity reflects the potential for significant business impact if misused—false attendance records could lead to incorrect payroll processing, compliance violations, or financial losses.

From the tool's definition Tool name explicitly states 'update_attendance_record' and description confirms it 'Update[s] an employee attendance/time tracking record'. The verb 'update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_attendance_record Rate-limited

update_attendance_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_attendance_record": {
      "limits": [
        {
          "counter": "update_attendance_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_attendance_record

What does the update_attendance_record tool do? +

Update an employee attendance/time tracking record in Sanka. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_attendance_record? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_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 update_attendance_record? +

update_attendance_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_attendance_record? +

Yes. Add a rate_limit block to the update_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 update_attendance_record completely? +

Set action: deny in the PolicyLayer policy for update_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 update_attendance_record? +

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