start_operator_passkey_enrollment

WHAT IT DOES

What start_operator_passkey_enrollment does on Run402

AI agents use start_operator_passkey_enrollment to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why start_operator_passkey_enrollment needs a policy

This tool sends an enrollment email and initiates a passkey enrollment flow — a Write action that creates a new authentication credential linkage. It does not delete or execute code, but misuse could allow an attacker to enroll an unauthorized passkey, granting persistent operator-level access. Severity is medium-to-high due to the security implications of operator credential enrollment.

From the tool's definition Email a short-lived Run402 operator passkey enrollment link to the verified contact email

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_operator_passkey_enrollment Rate-limited

start_operator_passkey_enrollment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_operator_passkey_enrollment": {
      "limits": [
        {
          "counter": "start_operator_passkey_enrollment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 start_operator_passkey_enrollment

What does the start_operator_passkey_enrollment tool do? +

Email a short-lived Run402 operator passkey enrollment link to the verified contact email. Requires email_verified. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on start_operator_passkey_enrollment? +

Register the Run402 MCP server in PolicyLayer and add a rule for start_operator_passkey_enrollment: 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 start_operator_passkey_enrollment? +

start_operator_passkey_enrollment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit start_operator_passkey_enrollment? +

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

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

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