Run Planner agent to generate a Markdown test plan from a target URL.
AI agents invoke run_planner to trigger actions in Mobile Testing AI Agent MCP Server. 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.
This tool triggers execution of a planning agent that processes a target URL and generates outputs (Markdown test plan). While the immediate action (plan generation) may seem benign, it executes an autonomous agent whose behavior depends on the supplied URL argument.
From the tool's definition Tool description states 'Run Planner agent' which indicates execution of an agent process. Combined with sibling tools like run_generator, run_healer, and run_orchestrator, this is part of an automated execution pipeline for mobile test automation.
Documented attack patterns abuse exactly the kind of access run_planner gives an agent:
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_planner:
{
"version": "1",
"default": "deny",
"tools": {
"run_planner": {
"limits": [
{
"counter": "run_planner_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_planner 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.
Free to start. No card required.
Run Planner agent to generate a Markdown test plan from a target URL. 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.
Register the Mobile Testing AI Agent MCP Server MCP server in PolicyLayer and add a rule for run_planner: 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.
run_planner is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_planner 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.
Set action: deny in the PolicyLayer policy for run_planner. 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.
run_planner 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.
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.
Free to start. No card required.
6 Mobile Testing AI Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.