Run Generator agent to create executable tests from a Markdown plan.
AI agents invoke run_generator 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 generates and executes test code based on input plans. While the primary output is test creation (which could be Write), the tool's role in a mobile test automation agent means the generated tests will be executed against real or simulated mobile applications.
From the tool's definition Tool name 'run_generator' combined with description 'create executable tests' indicates code generation and execution.
Documented attack patterns abuse exactly the kind of access run_generator 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_generator:
{
"version": "1",
"default": "deny",
"tools": {
"run_generator": {
"limits": [
{
"counter": "run_generator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} run_generator 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 Generator agent to create executable tests from a Markdown plan. 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_generator: 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_generator 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_generator 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_generator. 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_generator 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.