screenlog_process_model_save · Yaver MCP: Risk & Policy

WHAT IT DOES

What screenlog_process_model_save does on Yaver

AI agents use screenlog_process_model_save 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
`id`	string	Yes
`model`	object	Yes	the completed ProcessModel

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why screenlog_process_model_save needs a policy

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

screenlog_process_model_save Rate-limited

screenlog_process_model_save 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": {
    "screenlog_process_model_save": {
      "limits": [
        {
          "counter": "screenlog_process_model_save_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 screenlog_process_model_save

What does the screenlog_process_model_save tool do? +

Save a runner-completed ProcessModel for a session (episodes with intent/fields/decision-rules + machinery[] + role/system/summary). Stored locally at ~/.yaver/screenlog/<id>/process_model.json. 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 screenlog_process_model_save accept? +

screenlog_process_model_save accepts 2 parameters: id, model. Required: id, model. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on screenlog_process_model_save? +

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

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

Can I rate-limit screenlog_process_model_save? +

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

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

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