Open a TeamViewer-style remote-support window on this machine. Returns a 6-char code, a scoped bearer token, and shareable URLs. A guest who redeems the code gets terminal / exec / file-browse access for the TTL. Revoke anytime with support_stop.
AI agents call support_start to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ttl | string | — | Duration string (e.g. "30m", "2h"). Default 30m. |
label | string | — | Optional tag — e.g. "cousin" or "support-ticket-1234" — shown in status. |
Parameters from the server's own tool schema.
Even though support_start only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Open a TeamViewer-style remote-support window on this machine. Returns a 6-char code, a scoped bearer token, and shareable URLs. A guest who redeems the code gets terminal / exec / file-browse access for the TTL. Revoke anytime with support_stop. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
support_start accepts 2 parameters: ttl, label. 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 support_start: 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.
support_start is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the support_start 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 support_start. 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.
support_start 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.