managed_set · Yaver MCP: Risk & Policy

WHAT IT DOES

What managed_set does on Yaver

AI agents use managed_set 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.

PARAMETERS

Parameter	Type	Required	Description
`managed`	object	—	true \| false \| null
`subsystem`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why managed_set needs a policy

An AI agent can call managed_set faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

managed_set Rate-limited

managed_set 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": {
    "managed_set": {
      "limits": [
        {
          "counter": "managed_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about managed_set

What does the managed_set tool do? +

Set one subsystem's managed-flag. managed:true = use Yaver-hosted infra for this subsystem; managed:false = user-hosted; managed:null = clear the preference (revert to default). Valid subsystems: relay, dns, analytics, storage, email, ci, voice, llm. 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 managed_set accept? +

managed_set accepts 2 parameters: managed, subsystem. Required: subsystem. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on managed_set? +

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

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

Can I rate-limit managed_set? +

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

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

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