clock_punch · Attendance MCP: Risk & Policy

WHAT IT DOES

What clock_punch does on Attendance

AI agents invoke clock_punch to trigger actions in Attendance. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why clock_punch needs a policy

Based on the server description explicitly mentioning 'clock punch' as a core operation, this tool likely triggers an attendance clock-in or clock-out event in the HRMS system. This is an external operation with real-world side effects (modifying attendance records), placing it in the Execute category.

From the tool's definition Tool name 'clock_punch' on a server described as exposing 'clock punch' functionality; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clock_punch Rate-limited

clock_punch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clock_punch": {
      "limits": [
        {
          "counter": "clock_punch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 clock_punch

What does the clock_punch tool do? +

clock_punch. It is categorised as a Execute tool in the Attendance MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on clock_punch? +

Register the Attendance MCP server in PolicyLayer and add a rule for clock_punch: 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 clock_punch? +

clock_punch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clock_punch? +

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

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

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