local_ydb_pull_image
Plan or start a background Docker pull for a local-ydb image on the selected target. Without confirm=true it returns inspect and pull commands only; with confirm=true it returns a jobId for local_ydb_pull_status unless the image is already present.
This record as markdown: /tools/local-ydb/local-ydb-pull-image.md
What local_ydb_pull_image does on Local Ydb
AI agents invoke local_ydb_pull_image to trigger actions in Local Ydb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why local_ydb_pull_image is rated High
Pulling a Docker image is an external operation that modifies the local system state by downloading and storing container images. While not destructive (images can be removed) or financial, it is an Execute action because it triggers an external process (Docker daemon) to perform work.
From the tool's definition The tool description states it 'start[s] a background Docker pull' and 'returns a jobId for local_ydb_pull_status', indicating it executes an external Docker operation whose effects depend on arguments (the selected target and image).
Attacks that exploit this kind of access
The rule that runs local_ydb_pull_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local Ydb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For local_ydb_pull_image, this is the rule to start with:
local_ydb_pull_image stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local Ydb, apply this rule, and every local_ydb_pull_image call is checked against it from then on.
Questions about local_ydb_pull_image
Plan or start a background Docker pull for a local-ydb image on the selected target. Without confirm=true it returns inspect and pull commands only; with confirm=true it returns a jobId for local_ydb_pull_status unless the image is already present. It is categorised as a Execute tool in the Local Ydb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_pull_image: 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 Local Ydb. Nothing to install.
local_ydb_pull_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the local_ydb_pull_image 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 local_ydb_pull_image. 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.
local_ydb_pull_image is provided by the Local Ydb MCP server (@astandrik/local-ydb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local Ydb, and thousands of servers like it.
Across the catalogue