Update this machine's screenlog consent policy. Use enabled=false to hard-disable all recording, allow_remote_control to gate remote (same-account) start/stop, allow_input_capture to permit the keystroke/mouse companion stream (separate stronger gate — keylogging is sensitive), and allow_peer/rev...
AI agents use screenlog_policy_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
enabled | boolean | — | |
allow_peer | string | — | mesh peer/device id to grant screen access |
revoke_peer | string | — | |
notify_on_start | boolean | — | |
require_mesh_grant | boolean | — | |
allow_input_capture | boolean | — | |
allow_remote_control | boolean | — |
Parameters from the server's own tool schema.
An AI agent can call screenlog_policy_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
Update this machine's screenlog consent policy. Use enabled=false to hard-disable all recording, allow_remote_control to gate remote (same-account) start/stop, allow_input_capture to permit the keystroke/mouse companion stream (separate stronger gate — keylogging is sensitive), and allow_peer/revoke_peer to grant or remove a yaver-mesh peer's screen access (a mesh peering does NOT implicitly grant screen access). 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.
screenlog_policy_set accepts 7 parameters: enabled, allow_peer, revoke_peer, notify_on_start, require_mesh_grant, allow_input_capture, allow_remote_control. 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 screenlog_policy_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.
screenlog_policy_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the screenlog_policy_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.
Set action: deny in the PolicyLayer policy for screenlog_policy_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.
screenlog_policy_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.