This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-port.md
What docker_port does on Yaver
AI agents call docker_port to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
container | string | Yes |
Parameters from the server's own tool schema.
Why docker_port is rated Low
This tool only reads/displays existing Docker port mapping configuration. It has no side effects, does not create, modify, delete, or execute anything. It is purely informational, making it a Read category tool with low severity since port mapping information is not sensitive in most contexts and misuse would have minimal blast radius.
From the tool's definition Tool name 'docker_port' and description 'Show port mappings' indicate a query operation that retrieves and displays information about Docker container port mappings without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs docker_port 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_port, this is the rule to start with:
docker_port is read-only, so it stays allowed. 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_port call is checked against it from then on.
Questions about docker_port
Show port mappings. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
docker_port accepts 1 parameter: container. Required: container. 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_port: 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_port 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 docker_port 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_port. 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_port 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