services_start
Start all or specific local development services (Postgres, Redis, MinIO, etc.) from .yaver/services.yaml.
This record as markdown: /tools/io-github-kivanccakmak-yaver/services-start.md
What services_start does on Yaver
AI agents invoke services_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 |
|---|---|---|---|
names | array | — | Service names to start (empty = all) |
Parameters from the server's own tool schema.
Why services_start is rated High
This tool triggers the startup of system services whose behavior depends on the provided .yaver/services.yaml configuration. While local to development, starting services can consume resources, affect system state, and potentially interfere with other processes. This is Execute rather than Write because it invokes external operations/processes rather than creating/modifying data structures.
From the tool's definition Tool description states 'Start all or specific local development services' which invokes external operations (Postgres, Redis, MinIO, etc.). The ability to start services is an execution action with side effects that depend on configuration arguments.
Attacks that exploit this kind of access
The rule that runs services_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 services_start, this is the rule to start with:
services_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every services_start call is checked against it from then on.
Questions about services_start
Start all or specific local development services (Postgres, Redis, MinIO, etc.) from .yaver/services.yaml. 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.
services_start accepts 1 parameter: names. 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 services_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.
services_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the services_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.
Set action: deny in the PolicyLayer policy for services_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.
services_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.
More on Yaver, and thousands of servers like it.
Across the catalogue