stop_custom_app

THE RISK

High Risk

Why stop_custom_app needs a policy

While stopping an app doesn't permanently destroy data (ruling out Destructive), it executes a command that changes system state and availability. The operation has significant blast radius: stopping critical applications could disrupt services, affect dependent systems, or cause data loss if not handled carefully.

From the tool's definition Tool name 'stop_custom_app' with description 'Stop a running Custom App' indicates execution of a control operation that stops a running process/service. This is an external operation that triggers a state change in a Docker Compose application infrastructure.

Documented attack patterns abuse exactly the kind of access stop_custom_app gives an agent:

POLICY

How to control stop_custom_app

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 stop_custom_app:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_custom_app": {
      "limits": [
        {
          "counter": "stop_custom_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

stop_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.

Create a free account and register TrueNAS Scale MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More TrueNAS Scale MCP Server tools

Destructive delete_custom_app Delete a Custom App and optionally its data volumes Destructive cleanup_stale_containers Clean up stale containers and fix conflicts Execute bulk_app_operation Start/stop multiple apps at once Execute deploy_custom_app Deploy a new Custom App from Docker Compose configuration Execute start_custom_app Start a stopped Custom App Write update_custom_app Update an existing Custom App with new Docker Compose configuration Read diagnose_docker_issues Diagnose Docker engine issues and network conflicts Read get_app_logs Retrieve logs from a Custom App

All 13 TrueNAS Scale MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in TrueNAS Scale MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about stop_custom_app

What does the stop_custom_app tool do? +

Stop a running Custom App. 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.

How do I enforce a policy on stop_custom_app? +

Register the TrueNAS Scale MCP Server MCP server in PolicyLayer and add a rule for stop_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.

What risk level is stop_custom_app? +

stop_custom_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_custom_app? +

Yes. Add a rate_limit block to the stop_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.

How do I block stop_custom_app completely? +

Set action: deny in the PolicyLayer policy for stop_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.

What MCP server provides stop_custom_app? +

stop_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.

Enforce policy on every TrueNAS Scale MCP Server tool call.

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.

CHECK YOUR STACK →