// MCP TOOL REFERENCE

test_mobile

Run mobile app security testing (Android or iOS). Static + dynamic analysis. OWASP Mobile Top 10 coverage. Returns immediately with engagement_id; agent runs asynchronously.

ServerPentest Ai
CategoryExecute

How to control test_mobile ↓

WHAT TEST_MOBILE ON PENTEST AI DOES

AI agents invoke test_mobile to trigger actions in Pentest Ai. 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.

THE RISK

High Risk

This tool executes real security testing tools against mobile applications (Android/iOS), performing both static and dynamic analysis. It actively runs security scanners and potentially exploits vulnerabilities as part of a pentest engagement. The asynchronous execution model means it triggers external operations whose effects depend on arguments.

From the tool's definition 'Run mobile app security testing', 'Static + dynamic analysis', 'agent runs asynchronously'

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

HOW TO CONTROL TEST_MOBILE

PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for test_mobile:

policy.json

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

test_mobile 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 Pentest Ai — 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

More Pentest Ai tools

Execute run_probe run_probe Execute run_recon Start a reconnaissance scan against a target. Returns immediately with an engagement_ Execute run_tool Run a specific security tool against a target. Returns structured results that are au Execute start_campaign Start a multi-target campaign. Creates one engagement per target. Accepts a list of I Execute start_engagement Start a new pentest engagement against a target. AUTHORIZED TARGETS ONLY. This initia Execute authenticated_scan Run a deterministic authenticated web scan (no LLM required). Logs in, crawls same-ho Execute builtin_scan Run built-in security scans without requiring any external tools. Works immediately a Execute ensure_tools_installed ensure_tools_installed

All 51 Pentest Ai tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Frida Agent MCP execute

Go deeper

High-risk tools in Pentest Ai → 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the test_mobile tool do? +

Run mobile app security testing (Android or iOS). Static + dynamic analysis. OWASP Mobile Top 10 coverage. Returns immediately with engagement_id; agent runs asynchronously. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_mobile? +

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

What risk level is test_mobile? +

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

Can I rate-limit test_mobile? +

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

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

test_mobile is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pentest Ai tool call.

Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN PENTEST AI →

Free to start. No card required.

51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

test_mobile

// WHAT TEST_MOBILE ON PENTEST AI DOES

// THE RISK

// HOW TO CONTROL TEST_MOBILE

// EXPLORE