microservice_down
Stop/remove the durable units and schedules for a wrapped microservice project.
This record as markdown: /tools/io-github-kivanccakmak-yaver/microservice-down.md
What microservice_down does on Yaver
AI agents call microservice_down to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes |
Parameters from the server's own tool schema.
Why microservice_down is rated Critical
Irreversibly stops and removes microservice infrastructure components; cannot be undone without recreation.
From the tool's definition Stop/remove the durable units and schedules for a wrapped microservice project.
Attacks that exploit this kind of access
The rule that runs microservice_down 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_down, this is the rule to start with:
microservice_down is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every microservice_down call is checked against it from then on.
Questions about microservice_down
Stop/remove the durable units and schedules for a wrapped microservice project. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
microservice_down accepts 1 parameter: project. Required: project. 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 microservice_down: 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.
microservice_down is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the microservice_down 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 microservice_down. 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.
microservice_down 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