auth_dev_stop

Stop the local auth server.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-dev-stop.md

WHAT IT DOES

What auth_dev_stop does on Yaver

AI agents invoke auth_dev_stop 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.

RISK

Why auth_dev_stop is rated High

This tool executes an operation (stopping a process) whose effects depend on the target system state. While stopping a service is technically reversible (can be restarted), it triggers external operations and causes immediate disruption to system functionality. This falls under Execute rather than Write because it runs a command/action rather than creating or modifying data.

From the tool's definition Tool name 'auth_dev_stop' combined with description 'Stop the local auth server' indicates execution of a command that terminates a running service.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auth_dev_stop 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_stop, this is the rule to start with:

auth_dev_stop Rate-limited

auth_dev_stop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_dev_stop": {
      "limits": [
        {
          "counter": "auth_dev_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every auth_dev_stop call is checked against it from then on.

FAQ

Questions about auth_dev_stop

What does the auth_dev_stop tool do? +

Stop the local auth server. 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.

How do I enforce a policy on auth_dev_stop? +

Register the Yaver MCP server in PolicyLayer and add a rule for auth_dev_stop: 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_stop? +

auth_dev_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit auth_dev_stop? +

Yes. Add a rate_limit block to the auth_dev_stop 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_stop completely? +

Set action: deny in the PolicyLayer policy for auth_dev_stop. 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_stop? +

auth_dev_stop 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →