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...
Risk signalsBulk/mass operation — affects multiple targets
Part of the AndroJack MCP server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"gradle_dependency_checker": {
"limits": [
{
"counter": "gradle_dependency_checker_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full AndroJack MCP policy for all 22 tools.
These attack patterns abuse exactly the kind of access gradle_dependency_checker gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the AndroJack MCP server in PolicyLayer and add a rule for gradle_dependency_checker: 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 AndroJack MCP. Nothing to install.
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 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 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 server (VIKAS9793/androjack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 AndroJack MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.