This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-dev-users.md
What auth_dev_users does on Yaver
AI agents use auth_dev_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 |
|---|---|---|---|
role | string | — | |
email | string | — | |
action | string | Yes | list, create, or delete |
password | string | — |
Parameters from the server's own tool schema.
Why auth_dev_users is rated Medium
This tool creates or modifies user accounts in a local development authentication server, which is reversible (users can be deleted or re-created). It does not permanently destroy production data, nor does it execute arbitrary code or handle financial transactions.
From the tool's definition Tool manages test users in a local auth server. The word 'manage' typically encompasses creating, modifying, and potentially removing test user accounts.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs auth_dev_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 auth_dev_users, this is the rule to start with:
auth_dev_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 auth_dev_users call is checked against it from then on.
Questions about auth_dev_users
Manage test users in the local auth server. 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.
auth_dev_users accepts 4 parameters: role, 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 auth_dev_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.
auth_dev_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 auth_dev_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 auth_dev_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.
auth_dev_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