microservice_wrap

Create or update yaver.companion.yaml for a microservice and optionally arm it as a durable Yaver companion service (systemd user unit on Linux, launchd on macOS).

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 120 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/microservice-wrap.md

WHAT IT DOES

What microservice_wrap does on Yaver

AI agents use microservice_wrap 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
`arm`	boolean	—	Start/install the companion after writing.
`args`	array	—
`name`	string	—	Service name. Defaults to project slug.
`port`	integer	—
`repo`	string	—	Project/repo directory. Defaults to the MCP session working directory.
`write`	boolean	—	Write yaver.companion.yaml.
`ai_wrap`	boolean	—	Mark this service as an AI-wrapped companion target for agent-run analysis/ops.
`command`	string	—	Command to run, e.g. npm run worker. If omitted, Yaver uses detected services.
`durable`	boolean	—	Default true. Durable services become OS units.
`project`	string	—
`workdir`	string	—	Working directory, absolute or repo-relative. Defaults to repo.
`env_file`	string	—	Dotenv file path, repo-relative or absolute.

Parameters from the server's own tool schema.

RISK

Why microservice_wrap is rated Medium

Modifies service configuration and registers persistent systemd/launchd services affecting system startup and runtime behavior.

From the tool's definition Create or update yaver.companion.yaml, arm as durable service (systemd/launchd)

Risk signalsHigh parameter count (19 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

microservice_wrap Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "microservice_wrap": {
      "limits": [
        {
          "counter": "microservice_wrap_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about microservice_wrap

What does the microservice_wrap tool do? +

Create or update yaver.companion.yaml for a microservice and optionally arm it as a durable Yaver companion service (systemd user unit on Linux, launchd on macOS). 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.

What parameters does microservice_wrap accept? +

microservice_wrap accepts 12 parameters: arm, args, name, port, repo, write, ai_wrap, command, durable, project, workdir, env_file. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on microservice_wrap? +

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

microservice_wrap is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit microservice_wrap? +

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

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

microservice_wrap 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 678 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →