Update Docker/container runtime configuration. All fields are optional — only provide what you want to change.
AI agents use docker_config_update to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
This tool creates or modifies Docker/container runtime configuration reversibly. While configuration changes can have significant blast radius (affecting all containers), they are not inherently destructive (can be reverted) and do not delete data or trigger financial transactions. The 'Update' verb and optional field semantics indicate Write-class behavior.
From the tool's definition Tool name is 'docker_config_update' and description states 'Update Docker/container runtime configuration' — this modifies system configuration that controls container runtime behavior.
Documented attack patterns abuse exactly the kind of access docker_config_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for docker_config_update:
{
"version": "1",
"default": "deny",
"tools": {
"docker_config_update": {
"limits": [
{
"counter": "docker_config_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}docker_config_update 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.
Free to start. No card required.
Update Docker/container runtime configuration. All fields are optional — only provide what you want to change. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas MCP server in PolicyLayer and add a rule for docker_config_update: 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 Truenas. Nothing to install.
docker_config_update 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_config_update 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_config_update. 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_config_update is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.