Deploy a new Custom App from Docker Compose configuration
AI agents invoke deploy_custom_app to trigger actions in TrueNAS Scale MCP Server. 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.
Deployment of Docker Compose applications triggers external operations (container creation, image pulling, service startup) whose effects are determined by the configuration supplied. This is not a simple read operation, nor is it reversible without using delete_custom_app (making it Execute rather than Write).
From the tool's definition Tool deploys a new Custom App from Docker Compose configuration, which involves pulling images, creating containers, and starting services based on provided configuration.
Documented attack patterns abuse exactly the kind of access deploy_custom_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TrueNAS Scale MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_custom_app:
{
"version": "1",
"default": "deny",
"tools": {
"deploy_custom_app": {
"limits": [
{
"counter": "deploy_custom_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} deploy_custom_app 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.
Free to start. No card required.
Deploy a new Custom App from Docker Compose configuration. It is categorised as a Execute tool in the TrueNAS Scale MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TrueNAS Scale MCP Server MCP server in PolicyLayer and add a rule for deploy_custom_app: 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 Scale MCP Server. Nothing to install.
deploy_custom_app 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 deploy_custom_app 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 deploy_custom_app. 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.
deploy_custom_app is provided by the TrueNAS Scale MCP Server MCP server (svnstfns/truenas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TrueNAS Scale MCP Server, 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.
13 TrueNAS Scale MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.