Medium Risk

create_user

Create a new user in a PocketBase auth collection. Requires admin authentication.

How to control create_user ↓

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

Medium Risk

The tool creates new user records, which is a reversible modification of data (users can be deleted or modified later). It requires admin authentication, limiting casual misuse, but an AI agent with compromised admin credentials could create unauthorized users, potentially bypassing access controls or creating dormant accounts for later exploitation.

From the tool's definition Tool description states 'Create a new user in a PocketBase auth collection' — this is a creation operation that adds new data to the system reversibly.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access create_user gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PocketBase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_user:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_user": {
      "limits": [
        {
          "counter": "create_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register PocketBase MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the create_user tool do? +

Create a new user in a PocketBase auth collection. Requires admin authentication. It is categorised as a Write tool in the PocketBase MCP Server 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_user? +

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

What risk level is create_user? +

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

Can I rate-limit create_user? +

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

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

create_user is provided by the PocketBase MCP Server MCP server (ssakone/pb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PocketBase MCP Server tool call.

Deterministic rules across all 19 PocketBase MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 PocketBase MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.