gradle-dependencies
Shows the Gradle dependency tree with structured output per configuration.
This record as markdown: /tools/io-github-dave-london-lint/gradle-dependencies.md
What gradle-dependencies does on Lint
AI agents call gradle-dependencies to retrieve information from Lint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gradle-dependencies is rated Low
This tool retrieves and displays dependency information from a Gradle project without creating, modifying, deleting, or executing anything. It is purely informational, analogous to running 'gradle dependencies' in read-only mode. The blast radius of misuse is minimal—an AI agent cannot cause harm by querying dependency information.
From the tool's definition Tool shows dependency tree with structured output - a query/retrieval operation with no modification, deletion, or execution capability. Description explicitly states 'shows' (read-only) and produces 'structured output'.
Attacks that exploit this kind of access
The rule that runs gradle-dependencies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gradle-dependencies, this is the rule to start with:
gradle-dependencies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lint, apply this rule, and every gradle-dependencies call is checked against it from then on.
Questions about gradle-dependencies
Shows the Gradle dependency tree with structured output per configuration. It is categorised as a Read tool in the Lint MCP Server, which means it retrieves data without modifying state.
Register the Lint MCP server in PolicyLayer and add a rule for gradle-dependencies: 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 Lint. Nothing to install.
gradle-dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gradle-dependencies 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-dependencies. 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-dependencies is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lint, and thousands of servers like it.
This server
Across the catalogue