runner_auth_credentials_import

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-auth-credentials-import.md

WHAT IT DOES

What runner_auth_credentials_import does on Yaver

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.

RISK

Why runner_auth_credentials_import is rated Medium

This tool transfers authentication credentials (subscription tokens) to a remote machine. It writes/imports credential data to another system. While it is reversible in principle (credentials can be revoked), the act of copying auth tokens to remote machines carries high severity due to the risk of credential exposure or unauthorized access if misused by an AI agent — e.g., exfiltrating tokens to an…

From the tool's definition Copy a runner subscription token... from an already-signed-in machine to a remote one

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs runner_auth_credentials_import safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runner_auth_credentials_import, this is the rule to start with:

runner_auth_credentials_import Rate-limited

runner_auth_credentials_import 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": {
    "runner_auth_credentials_import": {
      "limits": [
        {
          "counter": "runner_auth_credentials_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every runner_auth_credentials_import call is checked against it from then on.

FAQ

Questions about runner_auth_credentials_import

What does the runner_auth_credentials_import tool do? +

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.

What parameters does runner_auth_credentials_import accept? +

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.

How do I enforce a policy on runner_auth_credentials_import? +

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.

What risk level is runner_auth_credentials_import? +

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

Can I rate-limit runner_auth_credentials_import? +

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.

How do I block runner_auth_credentials_import completely? +

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.

What MCP server provides runner_auth_credentials_import? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →