backend_stop

Stop PocketBase backend.

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/backend-stop.md

WHAT IT DOES

What backend_stop does on Yaver

AI agents invoke backend_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 backend_stop is rated High

Stopping a backend service is an Execute action: it runs a command to halt an external process, has immediate side effects (service downtime), and is not reversible without manual restart. It is not Destructive because no data is deleted or overwritten.

From the tool's definition Tool description states 'Stop PocketBase backend' — this triggers an external operation (stopping a running service) whose effects depend on the arguments passed and the current system state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

backend_stop Rate-limited

backend_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": {
    "backend_stop": {
      "limits": [
        {
          "counter": "backend_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 backend_stop call is checked against it from then on.

FAQ

Questions about backend_stop

What does the backend_stop tool do? +

Stop PocketBase backend. 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 backend_stop? +

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

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

Can I rate-limit backend_stop? +

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

Set action: deny in the PolicyLayer policy for backend_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 backend_stop? +

backend_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 →