passkey_login_verify · Run402 MCP: Risk & Policy

WHAT IT DOES

What passkey_login_verify does on Run402

AI agents invoke passkey_login_verify to trigger actions in Run402. 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 passkey_login_verify needs a policy

This tool performs authentication by verifying a WebAuthn/passkey assertion and creating an auth session. It triggers an external authentication operation with real side effects (session creation), making it Execute rather than Read. Misuse could allow unauthorized session creation or session hijacking, but it requires a valid WebAuthn assertion to succeed, limiting blast radius somewhat.

From the tool's definition 'Verify a browser WebAuthn assertion and return a normal Run402 auth session'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passkey_login_verify Rate-limited

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

FAQ

Questions about passkey_login_verify

What does the passkey_login_verify tool do? +

Verify a browser WebAuthn assertion and return a normal Run402 auth session. It is categorised as a Execute tool in the Run402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on passkey_login_verify? +

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

What risk level is passkey_login_verify? +

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

Can I rate-limit passkey_login_verify? +

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

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

passkey_login_verify is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

passkey_login_verify is one line of Run402's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →