stop_ap · Mitm MCP: Risk & Policy

WHAT IT DOES

What stop_ap does on Mitm

AI agents invoke stop_ap to trigger actions in Mitm. 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 stop_ap needs a policy

This tool invokes shell commands to terminate a running network service. While stopping a service is technically reversible (the AP can be restarted), the immediate effect of disrupting all connected clients and network access makes this an Execute category risk. The severity is high because an AI agent misusing this could disable network infrastructure, disconnect users, and disrupt IoT device operations.

From the tool's definition The tool executes a shell script (ap-toggle.sh) that controls a hostapd access point, a network daemon that requires system-level operations to start and stop.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_ap Rate-limited

stop_ap 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": {
    "stop_ap": {
      "limits": [
        {
          "counter": "stop_ap_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 Mitm, so you can run agents against it safely.

FAQ

Questions about stop_ap

What does the stop_ap tool do? +

Stop the hostapd access point via ap-toggle.sh. It is categorised as a Execute tool in the Mitm 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_ap? +

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

What risk level is stop_ap? +

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

Can I rate-limit stop_ap? +

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

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

stop_ap is provided by the Mitm MCP server (mplogas/mitmproxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.