stop_bridge

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke stop_bridge to trigger processes or run actions in Mobai. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON STOP_BRIDGE

stop_bridge can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-mobai-app-mobai-mcp.yaml

tools:
  stop_bridge:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mobai policy for all 23 tools.

// DETAILS

Tool Name stop_bridge

Category Execute

MCP Server Mobai MCP Server

Risk Level High

// MORE MOBAI TOOLS

Destructive uninstall_app Execute execute_dsl Execute start_bridge Write install_app Write save_screenshot Read get_device Read get_screenshot Read list_apps

View all 23 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like stop_bridge have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

stop_bridge is one of the high-risk operations in Mobai. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the stop_bridge tool do? +

Stop the automation bridge on a device. It is categorised as a Execute tool in the Mobai 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_bridge? +

Add a rule in your Intercept YAML policy under the tools section for stop_bridge. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mobai MCP server.

What risk level is stop_bridge? +

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

Can I rate-limit stop_bridge? +

Yes. Add a rate_limit block to the stop_bridge rule in your Intercept 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_bridge completely? +

Set action: deny in the Intercept policy for stop_bridge. 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_bridge? +

stop_bridge is provided by the Mobai MCP server (mobai-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mobai