CALL THIS AFTER GENERATING EVERY ANDROID CODE BLOCK. This is the Level 3 loop-back gate: validates AI-generated Kotlin, XML, and Gradle code against 24 Android-specific rules before the user sees it. Detects removed APIs (AsyncTask, TestCoroutineDispatcher), deprecated patterns (ContextualFlowRow...
Accepts freeform code/query input (code); Bulk/mass operation — affects multiple targets
Part of the AndroJack MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke android_code_validator to trigger processes or run actions in AndroJack MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
android_code_validator can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
android_code_validator:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: true See the full AndroJack MCP policy for all 22 tools.
Agents calling execute-class tools like android_code_validator have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
android_code_validator is one of the high-risk operations in AndroJack MCP. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
CALL THIS AFTER GENERATING EVERY ANDROID CODE BLOCK. This is the Level 3 loop-back gate: validates AI-generated Kotlin, XML, and Gradle code against 24 Android-specific rules before the user sees it. Detects removed APIs (AsyncTask, TestCoroutineDispatcher), deprecated patterns (ContextualFlowRow, NavController in new code, SharedPreferences), Android 16 violations (orientation locks, resizeableActivity=false), and structural issues (GlobalScope.launch, runBlocking in UI). Returns: verdict (PASS/WARN/FAIL), line-level violations with replacements and doc URLs, and explicit next-step instructions. If verdict is FAIL: fix all errors and re-run before returning code to the user. Inputs: code (required), language ('kotlin'|'xml'|'gradle', auto-detected if omitted), minSdk and targetSdk for context-aware API level checks.. It is categorised as a Execute tool in the AndroJack MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for android_code_validator. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AndroJack MCP MCP server.
android_code_validator 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 android_code_validator rule in your Intercept 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 Intercept policy for android_code_validator. 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.
android_code_validator is provided by the AndroJack MCP MCP server (androjack-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept