services_add
Add a service to the local stack. Presets: postgres, redis, minio, mailpit, umami, posthog, logto, meili, typesense.
This record as markdown: /tools/io-github-kivanccakmak-yaver/services-add.md
What services_add does on Yaver
AI agents use services_add to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Service name (use preset name for defaults) |
port | integer | — | Port (optional if using preset) |
image | string | — | Docker image (optional if using preset) |
Parameters from the server's own tool schema.
Why services_add is rated Medium
This tool creates or adds services to a local development stack, which is a reversible Write operation. It modifies the local environment by adding new services (database, cache, storage, email, analytics, etc.) but does not execute arbitrary code, delete resources, or move money.
From the tool's definition Tool name 'services_add' and description 'Add a service to the local stack' indicates creation of new infrastructure/configuration resources.
Attacks that exploit this kind of access
The rule that runs services_add 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_add, this is the rule to start with:
services_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_add call is checked against it from then on.
Questions about services_add
Add a service to the local stack. Presets: postgres, redis, minio, mailpit, umami, posthog, logto, meili, typesense. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
services_add accepts 3 parameters: name, port, image. Required: name. 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_add: 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_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the services_add 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_add. 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_add 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