Scan and index all Java classes from the project\
AI agents call scan_dependencies to retrieve information from Java Inspector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of Java dependencies by scanning and indexing classes. It retrieves information about the project's Java classes without modifying code, executing operations, or deleting data. The sibling tools (analyze_class, decompile_class, get_inheritance_tree, search_class) all support a Read-only analysis pattern.
From the tool's definition Tool name is 'scan_dependencies' and description states 'Scan and index all Java classes from the project' — uses 'scan' and 'index' which are retrieval/inspection operations with no modification or execution
Attacks that exploit this kind of access
Scan and index all Java classes from the project\. It is categorised as a Read tool in the Java Inspector MCP Server, which means it retrieves data without modifying state.
Register the Java Inspector MCP server in PolicyLayer and add a rule for scan_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 Java Inspector. Nothing to install.
scan_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 scan_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 scan_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.
scan_dependencies is provided by the Java Inspector MCP server (mustafagoksever/java-inspector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →