This record as markdown: /tools/io-github-kivanccakmak-yaver/backend-users.md
What backend_users does on Yaver
AI agents use backend_users to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | — | |
action | string | Yes | |
password | string | — |
Parameters from the server's own tool schema.
Why backend_users is rated Medium
PocketBase is a backend framework, and 'manage' authentication users implies the ability to create, modify, or alter user accounts and their properties. This is a reversible Write operation rather than Read (which would be 'list' or 'get' users) or Destructive (which would explicitly delete).
From the tool's definition Tool name is 'backend_users' with description 'Manage PocketBase auth users.' The verb 'Manage' in the context of authentication users typically encompasses create, update, and modify operations on user records.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs backend_users safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For backend_users, this is the rule to start with:
backend_users 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every backend_users call is checked against it from then on.
Questions about backend_users
Manage PocketBase auth users. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
backend_users accepts 3 parameters: email, action, password. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for backend_users: 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 Yaver. Nothing to install.
backend_users is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the backend_users 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.
Set action: deny in the PolicyLayer policy for backend_users. 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.
backend_users is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue