This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-cp.md
What docker_cp does on Yaver
AI agents use docker_cp 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 |
|---|---|---|---|
source | string | Yes | |
destination | string | Yes |
Parameters from the server's own tool schema.
Why docker_cp is rated Medium
docker_cp transfers files between the host filesystem and a Docker container. This is a write operation as it creates or modifies files in the destination (either host or container). It is reversible in principle (files can be deleted or overwritten again), so it does not qualify as Destructive. However, misuse could overwrite important container or host files, making severity medium.
From the tool's definition Copy files between host and container
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs docker_cp 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 docker_cp, this is the rule to start with:
docker_cp 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docker_cp call is checked against it from then on.
Questions about docker_cp
Copy files between host and container. 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.
docker_cp accepts 2 parameters: source, destination. Required: source, destination. 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 docker_cp: 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.
docker_cp 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 docker_cp 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 docker_cp. 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.
docker_cp 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue