submit_batch_ot_request · Attendance MCP: Risk & Policy

WHAT IT DOES

What submit_batch_ot_request does on Attendance

AI agents use submit_batch_ot_request 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_batch_ot_request needs a policy

This tool creates new OT (overtime) requests in batch, which are reversible writes to HR/payroll data (can be cancelled via 'cancel_ot_request'). It is not Destructive because submissions are cancellable. It is not Financial because OT approval and payment happen downstream (not direct fund movement).

From the tool's definition Tool name 'submit_batch_ot_request' indicates creation of multiple overtime requests. Sibling tools confirm context: 'approve_request', 'reject_request', 'cancel_ot_request', and 'get_ot_request' all operate on overtime requests within an HRMS/attendance…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_batch_ot_request Rate-limited

submit_batch_ot_request 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_batch_ot_request": {
      "limits": [
        {
          "counter": "submit_batch_ot_request_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_batch_ot_request

What does the submit_batch_ot_request tool do? +

submit_batch_ot_request. 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_batch_ot_request? +

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

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

Can I rate-limit submit_batch_ot_request? +

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

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

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