cancel_ot_request
AI agents call cancel_ot_request to permanently remove resources in Attendance — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an OT request is likely irreversible — once cancelled, the request record is removed or voided and may not be recoverable, affecting employee compensation and scheduling. The sibling tools (approve_request, reject_request, submit_batch_ot_request) suggest a workflow where cancellation terminates a request permanently.
From the tool's definition Tool name 'cancel_ot_request' and server context describing OT (overtime) request management. Description is empty and uninformative.
Attacks that exploit this kind of access
cancel_ot_request. It is categorised as a Destructive tool in the Attendance MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Attendance MCP server in PolicyLayer and add a rule for cancel_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.
cancel_ot_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_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.
Set action: deny in the PolicyLayer policy for cancel_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.
cancel_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →