This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-dev-setup.md
What auth_dev_setup does on Yaver
AI agents call auth_dev_setup to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
framework | string | — | nextjs, react, or generic |
Parameters from the server's own tool schema.
Why auth_dev_setup is rated Low
The tool retrieves or generates auth integration code for a frontend framework. This is a read/fetch operation that returns code for the developer to use; it does not execute, deploy, or modify any system state. Severity is low since it only provides code examples. Confidence is slightly reduced because 'setup' in the name could imply some configuration side effects, but the description clearly says 'Get... code'.
From the tool's definition 'Get auth integration code for your frontend framework' — retrieves/generates code snippets for display
Attacks that exploit this kind of access
The rule that runs auth_dev_setup 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_setup, this is the rule to start with:
auth_dev_setup is read-only, so it stays allowed. 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_setup call is checked against it from then on.
Questions about auth_dev_setup
Get auth integration code for your frontend framework. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
auth_dev_setup accepts 1 parameter: framework. 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_setup: 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_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the auth_dev_setup 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_setup. 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_setup 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