reject_leave · MCP Leave Management MCP: Risk & Policy

WHAT IT DOES

What reject_leave does on MCP Leave Management

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

WHY IT NEEDS A POLICY

Why reject_leave needs a policy

The reject_leave operation creates or modifies data (a leave request's status) in a reversible manner. While it affects employee records and workflow state, rejection does not permanently delete data or commit financial obligations; it is a Write-category action. Severity is medium because misuse could disrupt an employee's leave workflow, but the action is typically reversible (leave can be reapplied or escalated).

From the tool's definition The tool is described as a proxy for 'reject_leave' in a leave management workflow. Rejection of a leave application modifies the state of that application reversibly—a rejected leave can typically be reapplied.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_leave Rate-limited

reject_leave 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": {
    "reject_leave": {
      "limits": [
        {
          "counter": "reject_leave_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 MCP Leave Management, so you can run agents against it safely.

FAQ

Questions about reject_leave

What does the reject_leave tool do? +

Proxy reject_leave to the leave-management leaf MCP. It is categorised as a Write tool in the MCP Leave Management MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reject_leave? +

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

What risk level is reject_leave? +

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

Can I rate-limit reject_leave? +

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

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

reject_leave is provided by the MCP Leave Management MCP server (jaylathiatr/mcp-leave-management). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.