This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-dev-tokens.md
What auth_dev_tokens does on Yaver
AI agents invoke auth_dev_tokens to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | — | User email (for generate) |
token | string | — | JWT token (for inspect) |
action | string | Yes | generate or inspect |
Parameters from the server's own tool schema.
Why auth_dev_tokens is rated High
Generating JWT tokens is an execution action that produces security credentials used for API authentication. Misuse could allow unauthorized API access by creating valid tokens. It is not a simple read (it generates new artifacts) and not purely write (tokens are security primitives with operational impact).
From the tool's definition 'Generate or inspect JWT tokens for API testing' — generating tokens is an active operation that creates security credentials
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs auth_dev_tokens 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_tokens, this is the rule to start with:
auth_dev_tokens stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_tokens call is checked against it from then on.
Questions about auth_dev_tokens
Generate or inspect JWT tokens for API testing. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
auth_dev_tokens accepts 3 parameters: email, token, action. 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_tokens: 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_tokens is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the auth_dev_tokens 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_tokens. 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_tokens 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.
Across the catalogue