routine_update · Yaver MCP: Risk & Policy

WHAT IT DOES

What routine_update does on Yaver

AI agents use routine_update 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
`id`	string	Yes
`cron`	string	—
`name`	string	—
`run_at`	string	—
`machine`	string	—
`payload`	object	—
`max_runs`	integer	—
`repeat_interval`	integer	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why routine_update needs a policy

An AI agent can call routine_update 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.

Risk signalsAccepts raw HTML/template content (payload)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

routine_update Rate-limited

routine_update 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": {
    "routine_update": {
      "limits": [
        {
          "counter": "routine_update_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 routine_update

What does the routine_update tool do? +

Partial update of a routine's mutable fields. Supply only the fields you want to change; omitted fields are preserved. Setting cron/run_at/repeat_interval triggers an immediate NextRunAt recompute. 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 routine_update accept? +

routine_update accepts 8 parameters: id, cron, name, run_at, machine, payload, max_runs, repeat_interval. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on routine_update? +

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

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

Can I rate-limit routine_update? +

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

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

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