Run test for the Android project in the folder
AI agents invoke test to trigger actions in Android Project 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.
Running tests executes code and commands in the project environment. While tests are generally safe, they can trigger side effects depending on implementation (network calls, file I/O, device interactions). This is an Execute action since it runs code whose effects depend on the project's test suite.
From the tool's definition "Run test for the Android project" - executes test suite/commands against an Android project
Documented attack patterns abuse exactly the kind of access test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Project MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test:
{
"version": "1",
"default": "deny",
"tools": {
"test": {
"limits": [
{
"counter": "test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test 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 test for the Android project in the folder. It is categorised as a Execute tool in the Android Project MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Project MCP Server MCP server in PolicyLayer and add a rule for test: 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 Android Project MCP Server. Nothing to install.
test 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 test 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 test. 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.
test is provided by the Android Project MCP Server MCP server (shenghaiwang/androidbuild). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Project 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.
3 Android Project MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.