auth_wait · CIB Seven MCP Server MCP: Risk & Policy

WHAT IT DOES

What auth_wait does on CIB Seven MCP Server

AI agents invoke auth_wait to trigger actions in CIB Seven 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 auth_wait needs a policy

This tool executes an authentication flow that communicates with Keycloak and blocks execution pending completion. While not destructive or financial, it actively triggers an external operation (headless login) whose success depends on system state and whose outcome affects subsequent access privileges. This fits the Execute category (triggers external operations whose effects depend on arguments/context).

From the tool's definition Tool description states it 'Block[s] until a headless login started via auth_login(headless=true) completes.' This describes triggering and waiting for an external authentication operation to complete, which is an invocation of a system function with side…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_wait Rate-limited

auth_wait 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": {
    "auth_wait": {
      "limits": [
        {
          "counter": "auth_wait_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 CIB Seven MCP Server, so you can run agents against it safely.

FAQ

Questions about auth_wait

What does the auth_wait tool do? +

Block until a headless login started via auth_login(headless=true) completes. Fails if the login times out (2 min) or errors. It is categorised as a Execute tool in the CIB Seven 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 auth_wait? +

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

What risk level is auth_wait? +

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

Can I rate-limit auth_wait? +

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

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

auth_wait is provided by the CIB Seven MCP Server MCP server (krixerx/cib7-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.