Low Risk

java_get_hover

Get hover information for a symbol.

Accepts file system path (filePath)

Part of the Java Jdtls MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call java_get_hover to retrieve information from Java Jdtls without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though java_get_hover only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

java-jdtls.yaml
tools:
  java_get_hover:
    rules:
      - action: allow

See the full Java Jdtls policy for all 15 tools.

Tool Name java_get_hover
Category Read
Risk Level Low

View all 15 tools →

Agents calling read-class tools like java_get_hover have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the java_get_hover tool do? +

Get hover information for a symbol.. It is categorised as a Read tool in the Java Jdtls MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on java_get_hover? +

Add a rule in your Intercept YAML policy under the tools section for java_get_hover. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Java Jdtls MCP server.

What risk level is java_get_hover? +

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

Can I rate-limit java_get_hover? +

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

How do I block java_get_hover completely? +

Set action: deny in the Intercept policy for java_get_hover. 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 java_get_hover? +

java_get_hover is provided by the Java Jdtls MCP server (@sachiewonder/java-jdtls-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Java Jdtls

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.