submit_clock_amendment · Attendance MCP: Risk & Policy

WHAT IT DOES

What submit_clock_amendment does on Attendance

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

WHY IT NEEDS A POLICY

Why submit_clock_amendment needs a policy

Submitting a clock amendment creates or modifies attendance time records (reversible write operation). While not destructive (amendments can be corrected), it alters employee work records that feed payroll and compliance systems. Severity is medium because amendments are typically auditable and reversible, and the proxy authentication limits unauthorized access.

From the tool's definition Tool name 'submit_clock_amendment' indicates modification of clock/attendance records; sibling tools include 'clock_punch', 'approve_request', and 'cancel_ot_request', establishing this as an attendance/HRMS data mutation tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_clock_amendment Rate-limited

submit_clock_amendment 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": {
    "submit_clock_amendment": {
      "limits": [
        {
          "counter": "submit_clock_amendment_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 Attendance, so you can run agents against it safely.

FAQ

Questions about submit_clock_amendment

What does the submit_clock_amendment tool do? +

submit_clock_amendment. It is categorised as a Write tool in the Attendance MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_clock_amendment? +

Register the Attendance MCP server in PolicyLayer and add a rule for submit_clock_amendment: 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 Attendance. Nothing to install.

What risk level is submit_clock_amendment? +

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

Can I rate-limit submit_clock_amendment? +

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

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

submit_clock_amendment is provided by the Attendance MCP server (wenmaubipo/attendance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.