// SCAN REPORT

Passgage MCP Server

16 tools. 11 can modify or destroy data without limits.

11 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

11 can modify or destroy data

5 read-only

16 tools total

Community server · catalogue entry verified 30/06/2026

How to control Passgage MCP Server ↓

TOOL MAP

What Passgage MCP Server exposes to your agents

Read (5) Write / Execute (11) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Passgage MCP Server tools

Execute · High passgage_login This tool authenticates against an external API using credentials and returns a JWT token. Execute · Medium passgage_logout Logging out invalidates the current session token, which is an external operation with side effects (session termination). Execute · Medium passgage_switch_to_company_mode This tool changes the authentication mode of the system, triggering an operational state change that affects how all subsequent API calls are authenticated. Execute · Medium passgage_switch_to_user_mode This tool changes the authentication context/mode of the session, switching to a different JWT token.

11 of Passgage MCP Server's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Passgage MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Passgage MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "passgage_approve_request": {
    "limits": [
      {
        "counter": "passgage_approve_request_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "passgage_auth_status": {
    "limits": [
      {
        "counter": "passgage_auth_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Passgage MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PASSGAGE →

Instant setup, no code required.

FULL CATALOGUE

All 16 Passgage MCP Server tools

EXECUTE 4 tools

Execute passgage_login Login to Passgage API with email and password to get JWT token Execute passgage_logout Logout from Passgage API and invalidate the current session Execute passgage_switch_to_company_mode Switch to company API key authentication mode (requires previous API key setup) Execute passgage_switch_to_user_mode Switch to user JWT authentication mode (requires previous user login)

WRITE 7 tools

Write passgage_approve_request Approve or reject a pending approval request Write passgage_assign_user_to_shift Assign a user to a specific shift Write passgage_bulk_approve Approve or reject multiple approval requests at once Write passgage_refresh_token Refresh the current JWT token to extend its validity Write passgage_set_company_mode Switch to company API key authentication mode Write passgage_track_entrance Record an entrance/exit event for a user Write passgage_upload_file Upload a file to Passgage using presigned URL

READ 5 tools

Read passgage_auth_status Check authentication status, current mode, and available authentication methods Read passgage_export_data Export data in various formats (CSV, JSON, Excel) Read passgage_get_auth_modes Get available authentication modes and their status Read passgage_get_dashboard_stats Get dashboard statistics and key metrics Read passgage_search Universal search across multiple Passgage resources

FAQ

Questions about Passgage MCP Server

How do I prevent bulk modifications through Passgage MCP Server? +

The Passgage MCP Server server has 7 write tools including passgage_approve_request, passgage_assign_user_to_shift, passgage_bulk_approve. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Passgage MCP Server.

How many tools does the Passgage MCP Server MCP server expose? +

16 tools across 2 categories: Read, Write. 5 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Passgage MCP Server? +

Register the Passgage MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Passgage MCP Server tool call.

Deterministic rules across all 16 Passgage MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PASSGAGE →

Instant setup, no code required.

16 Passgage MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.