app_redeploy
Redeploy an app, recreating its containers with the current configuration.
This record as markdown: /tools/spranab-truenas-mcp/app-redeploy.md
What app_redeploy does on Truenas
AI agents invoke app_redeploy to trigger actions in Truenas. 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 app_redeploy is rated High
Redeploying an app involves stopping existing containers and recreating them, which triggers external operations (container orchestration). This is an Execute-level action with high severity as it causes service interruption and restarts production workloads.
From the tool's definition Redeploy an app, recreating its containers with the current configuration.
Attacks that exploit this kind of access
The rule that runs app_redeploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_redeploy, this is the rule to start with:
app_redeploy 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 Truenas, apply this rule, and every app_redeploy call is checked against it from then on.
Questions about app_redeploy
Redeploy an app, recreating its containers with the current configuration. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Truenas MCP server in PolicyLayer and add a rule for app_redeploy: 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.
app_redeploy 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 app_redeploy 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 app_redeploy. 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.
app_redeploy 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.
More on Truenas, and thousands of servers like it.
Across the catalogue