Copy a runner subscription token (Claude Max / Pro, or ChatGPT Plus / Pro for codex) from an already-signed-in machine to a remote one. Yaver is a single-user wrapper, so this is the preferred path when the user already has working subscription auth locally — it avoids re-running OAuth on every b...
AI agents use runner_auth_credentials_import 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 |
|---|---|---|---|
runner | string | Yes | |
device_id | string | — | Optional remote device ID. When omitted, writes to the local agent. |
credentials_json | string | Yes | The full credentials JSON blob — for claude on macOS this is the 'Claude Code-credentials' Keychain entry contents (or ~/.claude/.credentials.json on Linux); fo |
Parameters from the server's own tool schema.
An AI agent can call runner_auth_credentials_import 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
Copy a runner subscription token (Claude Max / Pro, or ChatGPT Plus / Pro for codex) from an already-signed-in machine to a remote one. Yaver is a single-user wrapper, so this is the preferred path when the user already has working subscription auth locally — it avoids re-running OAuth on every box (which hits the SSH-launched-daemon Keychain wall on macOS). Subscription only; never use API keys. 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.
runner_auth_credentials_import accepts 3 parameters: runner, device_id, credentials_json. Required: runner, credentials_json. 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 runner_auth_credentials_import: 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.
runner_auth_credentials_import 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 runner_auth_credentials_import 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 runner_auth_credentials_import. 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.
runner_auth_credentials_import 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.