send_clock_reminders · Attendance MCP: Risk & Policy

WHAT IT DOES

What send_clock_reminders does on Attendance

AI agents invoke send_clock_reminders 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 send_clock_reminders needs a policy

The name implies triggering outbound notifications/reminders to employees about clocking in/out, which constitutes an external operation (sending messages). This is most consistent with Execute. However, the empty description significantly reduces confidence. It could also be Write if it merely queues a record. Severity is medium as misuse could spam employees with unwanted reminders.

From the tool's definition Tool name 'send_clock_reminders' on a server with clock_punch and attendance tools; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_clock_reminders Rate-limited

send_clock_reminders 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": {
    "send_clock_reminders": {
      "limits": [
        {
          "counter": "send_clock_reminders_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 send_clock_reminders

What does the send_clock_reminders tool do? +

send_clock_reminders. 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 send_clock_reminders? +

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

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

Can I rate-limit send_clock_reminders? +

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

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

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