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 SOURCE0xsteph/pentest-ai
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/test-mobile.md

What test_mobile does on Pentest Ai

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.

Why test_mobile is rated High

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'

Questions about test_mobile

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.

More on Pentest Ai, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pentest Ai's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.