run_healer

THE RISK

High Risk

Why run_healer needs a policy

This tool triggers execution of an automated test healing agent that both runs tests (Execute) and modifies test code or state through auto-repair logic (Write-like effects). The primary action is Execute — invoking an external test automation process whose behavioral outcome depends on the target app, test suite, and repair logic. Auto-repair implies the tool may write changes back to test files or state.

From the tool's definition 'Run Healer agent to execute and auto-repair failing tests' — the tool executes test automation workflows and modifies test artifacts (repairs/auto-fixes failing tests), which are side-effects that depend on test state and configuration arguments.

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

POLICY

How to control run_healer

PolicyLayer is an MCP gateway — it sits between your AI agents and Mobile Testing AI Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_healer:

policy.json

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

run_healer 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 Mobile Testing AI Agent 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 Mobile Testing AI Agent MCP Server tools

Execute run_generator Run Generator agent to create executable tests from a Markdown plan. Execute run_orchestrator Run Android or iOS orchestration pipeline (Planner -> Generator -> Healer). Execute run_planner Run Planner agent to generate a Markdown test plan from a target URL. Read health_check Get basic MCP server and environment health information. Read list_repo_commands Return frequently used npm commands for this repository.

All 6 Mobile Testing AI Agent 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 Mobile Testing AI Agent 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 run_healer

What does the run_healer tool do? +

Run Healer agent to execute and auto-repair failing tests. It is categorised as a Execute tool in the Mobile Testing AI Agent 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 run_healer? +

Register the Mobile Testing AI Agent MCP Server MCP server in PolicyLayer and add a rule for run_healer: 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 Mobile Testing AI Agent MCP Server. Nothing to install.

What risk level is run_healer? +

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

Can I rate-limit run_healer? +

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

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

run_healer is provided by the Mobile Testing AI Agent MCP Server MCP server (padmarajnidagundi/mobile-app-testing-ai-agent-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 Mobile Testing AI Agent MCP Server tool call.

Start from Mobile Testing AI Agent 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 →