setup_tcp_port · MCP Emulator Controller MCP: Risk & Policy

WHAT IT DOES

What setup_tcp_port does on MCP Emulator Controller

AI agents invoke setup_tcp_port to trigger actions in MCP Emulator Controller. 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 setup_tcp_port needs a policy

Setting up TCP port forwarding is an Execute-category action because it configures network infrastructure on an Android emulator/device, creating persistent port mappings that affect network traffic routing. It is not merely reading data, nor is it directly destructive or financial, but it triggers an external operation (ADB port forwarding) whose effects depend on the arguments provided (port numbers, protocol).

From the tool's definition 'Setup TCP port forwarding for device' — configures network routing/forwarding on the device, which is an external system operation with side effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_tcp_port Rate-limited

setup_tcp_port 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": {
    "setup_tcp_port": {
      "limits": [
        {
          "counter": "setup_tcp_port_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 MCP Emulator Controller, so you can run agents against it safely.

FAQ

Questions about setup_tcp_port

What does the setup_tcp_port tool do? +

Setup TCP port forwarding for device. It is categorised as a Execute tool in the MCP Emulator Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on setup_tcp_port? +

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

What risk level is setup_tcp_port? +

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

Can I rate-limit setup_tcp_port? +

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

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

setup_tcp_port is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.