Low Risk

get_dependencies

Get Maven dependencies from POM files

How to control get_dependencies ↓

What get_dependencies does on Maven Decoder MCP Server

AI agents call get_dependencies to retrieve information from Maven Decoder MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_dependencies needs a policy

This tool queries and retrieves dependency information from Maven POM (Project Object Model) files without creating, modifying, executing, or deleting anything. It is a read-only operation that provides metadata about project dependencies. The blast radius of misuse is minimal—an agent could only gather information about dependencies, not affect systems or data.

From the tool's definition Tool name 'get_dependencies' and description 'Get Maven dependencies from POM files' indicate purely informational retrieval. The verb 'Get' combined with the source (POM files, which are static configuration) shows no modification, execution, or deletion.

Documented attack patterns abuse exactly the kind of access get_dependencies gives an agent:

How to control get_dependencies

PolicyLayer is an MCP gateway — it sits between your AI agents and Maven Decoder MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dependencies:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dependencies": {}
  }
}

get_dependencies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Maven Decoder MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dependencies

What does the get_dependencies tool do? +

Get Maven dependencies from POM files. It is categorised as a Read tool in the Maven Decoder MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dependencies? +

Register the Maven Decoder MCP Server MCP server in PolicyLayer and add a rule for get_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 Maven Decoder MCP Server. Nothing to install.

What risk level is get_dependencies? +

get_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dependencies? +

Yes. Add a rate_limit block to the get_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.

How do I block get_dependencies completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_dependencies? +

get_dependencies is provided by the Maven Decoder MCP Server MCP server (salitaba/maven-decoder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Maven Decoder MCP Server tool call.

Start from Maven Decoder 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.

14 Maven Decoder MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.