app_stop_server · Goose App Maker MCP: Risk & Policy

WHAT IT DOES

What app_stop_server does on Goose App Maker MCP

AI agents invoke app_stop_server to trigger actions in Goose App Maker MCP. 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 IT NEEDS A POLICY

Why app_stop_server needs a policy

This tool executes a command that stops an active HTTP server, which is a real-world operation with side effects. It does not merely query data (Read), create reversible changes (Write), or permanently delete data (Destructive). The severity is high because stopping a production HTTP server could disrupt service availability and affect multiple users or dependent systems.

From the tool's definition "Stop the currently running HTTP server" indicates the tool triggers an external operation (halting a running service) whose effects are immediate and state-changing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

app_stop_server Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Goose App Maker MCP, so you can run agents against it safely.

FAQ

Questions about app_stop_server

What does the app_stop_server tool do? +

Stop the currently running HTTP server. It is categorised as a Execute tool in the Goose App Maker MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on app_stop_server? +

Register the Goose App Maker MCP server in PolicyLayer and add a rule for app_stop_server: 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 Goose App Maker MCP. Nothing to install.

What risk level is app_stop_server? +

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

Can I rate-limit app_stop_server? +

Yes. Add a rate_limit block to the app_stop_server 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 app_stop_server completely? +

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

app_stop_server is provided by the Goose App Maker MCP server (michaelneale/goose-app-maker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.