Live version lookup for any Android, Kotlin, or Jetpack library from Google Maven and Maven Central. ALWAYS call this before adding or updating any dependency in build.gradle.kts. This tool exists because AI tools generate stale dependency coordinates. Known failures: wrong Coil group (io.coil-kt...
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 gradle_dependency_checker 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.
gradle_dependency_checker 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:
gradle_dependency_checker:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AndroJack MCP policy for all 22 tools.
Agents calling execute-class tools like gradle_dependency_checker 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.
gradle_dependency_checker 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.
Live version lookup for any Android, Kotlin, or Jetpack library from Google Maven and Maven Central. ALWAYS call this before adding or updating any dependency in build.gradle.kts. This tool exists because AI tools generate stale dependency coordinates. Known failures: wrong Coil group (io.coil-kt vs io.coil-kt.coil3 for Coil 3), missing BOM platform() wrapper for Compose and Firebase, outdated Compose BOM (moves every month), KAPT coordinates when KSP is the current standard, wrong artifact names for Room KMP vs Room Android. Returns: latest stable version, ready-to-paste Kotlin DSL, BOM resolution for managed artifacts, and KMP vs Android-only distinction where relevant. Examples: 'compose', 'hilt', 'room', 'retrofit', 'coil', 'lifecycle', 'coroutines', 'navigation', 'firebase'.. 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 gradle_dependency_checker. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AndroJack MCP MCP server.
gradle_dependency_checker 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 gradle_dependency_checker 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 gradle_dependency_checker. 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.
gradle_dependency_checker 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