auth · Zion MCP: Risk & Policy

WHAT IT DOES

What auth does on Zion

AI agents invoke auth to trigger actions in Zion. 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.

PARAMETERS

Parameter	Type	Required	Description
`op`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why auth needs a policy

This tool performs authentication operations including browser-based login flows, saving/deleting credentials, and session management. These are external operations with side effects (credential storage, session state changes). LOGOUT and REAUTH destructively delete credentials, but since the tool can also re-authenticate, the dominant behavior is Execute (triggering external auth flows and session operations).

From the tool's definition LOGIN (browser login + save credentials) | LOGOUT (delete credentials, unload sessions) | REAUTH (delete credentials and log in again)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth Rate-limited

auth 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": {
      "limits": [
        {
          "counter": "auth_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 Zion, so you can run agents against it safely.

FAQ

Questions about auth

What does the auth tool do? +

Authentication. op: LOGIN (browser login + save credentials) | LOGOUT (delete credentials, unload sessions) | WHOAMI (show authenticated account token payload) | REAUTH (delete credentials and log in again). It is categorised as a Execute tool in the Zion MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does auth accept? +

auth accepts 1 parameter: op. Required: op. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on auth? +

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

What risk level is auth? +

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

Can I rate-limit auth? +

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

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

auth is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.