passgage_login · Passgage MCP Server MCP: Risk & Policy

WHAT IT DOES

What passgage_login does on Passgage MCP Server

AI agents invoke passgage_login to trigger actions in Passgage MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why passgage_login needs a policy

This tool authenticates against an external API using credentials and returns a JWT token. It triggers an external operation (authentication session creation) and the resulting token can be misused to perform privileged actions across 130+ tools. While not directly destructive or financial, it establishes an authenticated session that enables all downstream operations, making misuse high severity.

From the tool's definition Login to Passgage API with email and password to get JWT token

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passgage_login Rate-limited

passgage_login stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_login": {
      "limits": [
        {
          "counter": "passgage_login_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_login

What does the passgage_login tool do? +

Login to Passgage API with email and password to get JWT token. It is categorised as a Execute tool in the Passgage MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on passgage_login? +

Register the Passgage MCP Server MCP server in PolicyLayer and add a rule for passgage_login: 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_login? +

passgage_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit passgage_login? +

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

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

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