create_auth_user · Run402 MCP: Risk & Policy

WHAT IT DOES

What create_auth_user does on Run402

AI agents use create_auth_user 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 create_auth_user needs a policy

The tool performs create/update operations on authentication users and permissions, which are Write-category actions. Severity is high because granting admin roles or issuing trusted invites could elevate an AI agent's privileges or create unauthorized access paths if misused, affecting infrastructure access control across the X402 coding agent platform.

From the tool's definition Tool creates or updates project auth users with service key, can assign project_admin role and send trusted invites. These are reversible data modifications (users can be removed, roles changed, invites revoked).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_auth_user Rate-limited

create_auth_user 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": {
    "create_auth_user": {
      "limits": [
        {
          "counter": "create_auth_user_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 create_auth_user

What does the create_auth_user tool do? +

Create or update a project auth user with the service key. Can set project_admin and optionally send a trusted invite. 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 create_auth_user? +

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

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

Can I rate-limit create_auth_user? +

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

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

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