auth_dev_tokens

Generate or inspect JWT tokens for API testing.

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 31 required

What auth_dev_tokens does on Yaver

AI agents call auth_dev_tokens to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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 needs a policy

Even though auth_dev_tokens only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHandles credentials or secrets (token)

Questions about auth_dev_tokens

What does the auth_dev_tokens tool do? +

Generate or inspect JWT tokens for API testing. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does auth_dev_tokens accept? +

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.

How do I enforce a policy on auth_dev_tokens? +

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.

What risk level is auth_dev_tokens? +

auth_dev_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit auth_dev_tokens? +

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.

How do I block auth_dev_tokens completely? +

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.

What MCP server provides auth_dev_tokens? +

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.