passgage_approve_request · Passgage MCP Server MCP

WHAT IT DOES

What passgage_approve_request does on Passgage MCP Server

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

WHY IT NEEDS A POLICY

Why passgage_approve_request needs a policy

This tool changes data state (approval status of a request) in a workforce management system. It is Write rather than Execute because it performs a specific business operation (approval decision) rather than arbitrary code execution. Severity is high because erroneous approvals in HR/workforce systems can lead to unauthorized time off, access, or payroll changes affecting multiple employees.

From the tool's definition Tool description states 'Approve or reject a pending approval request' - this modifies the state of an approval request in the system. The action is reversible (can be reversed by rejecting or re-approving), and affects workflow/HR processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passgage_approve_request Rate-limited

passgage_approve_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": {
    "passgage_approve_request": {
      "limits": [
        {
          "counter": "passgage_approve_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 Passgage MCP Server, so you can run agents against it safely.

FAQ

Questions about passgage_approve_request

What does the passgage_approve_request tool do? +

Approve or reject a pending approval request. It is categorised as a Write tool in the Passgage MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on passgage_approve_request? +

Register the Passgage MCP Server MCP server in PolicyLayer and add a rule for passgage_approve_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 Passgage MCP Server. Nothing to install.

What risk level is passgage_approve_request? +

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

Can I rate-limit passgage_approve_request? +

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

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

passgage_approve_request is provided by the Passgage MCP Server MCP server (passgage/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.