backend_start

Start PocketBase backend (built-in DB + auth + storage + realtime).

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 20 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-start.md

WHAT IT DOES

What backend_start does on Yaver

AI agents invoke backend_start 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
`mode`	string	—	Mode: standalone, docker (default: standalone)
`port`	integer	—	Port (default: 8090)

Parameters from the server's own tool schema.

RISK

Why backend_start is rated High

This is Execute rather than Write because it runs/starts a service process rather than creating or modifying data directly. The blast radius is high: a misconfigured or maliciously-timed backend start could expose databases, authentication systems, and storage services to unauthorized access, cause service disruption, or enable further attacks on the local development environment.

From the tool's definition The tool description states 'Start PocketBase backend' which initiates an external service with database, authentication, storage, and realtime capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

backend_start Rate-limited

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

FAQ

Questions about backend_start

What does the backend_start tool do? +

Start PocketBase backend (built-in DB + auth + storage + realtime). 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.

What parameters does backend_start accept? +

backend_start accepts 2 parameters: mode, port. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on backend_start? +

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

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

Can I rate-limit backend_start? +

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

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

backend_start 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

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_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 →