15 tools from the Java Jdtls MCP Server, categorised by risk level.
View the Java Jdtls policy →find_references Find references for a symbol. This is an enhanced version of java_get_references that marks external library results. 2/5 java_get_definition Get definition location for a symbol. 2/5 java_get_diagnostics Get diagnostics (errors/warnings) for a file. This tool now attempts to pull diagnostics actively from the server if supported (LSP 3.17+), otherwi... 2/5 java_get_file_symbols Get all symbols (classes, methods, fields) defined in a specific file. java_get_hover Get hover information for a symbol. 2/5 java_get_references Get references for a symbol. 2/5 java_get_status Get the current status of the Java Language Server. java_get_workspace_diagnostics Pull diagnostics for the entire workspace (LSP 3.17+). Note: This may not be supported by all language server versions. 2/5 java_load_maven_project Load a Maven Java project into the language server workspace. This causes JDTLS to index the project, resolving dependencies and symbols across the... 2/5 java_search_symbols Search for symbols (classes, methods, fields) across the entire workspace by name. 2/5 read_java_content Read the content of a Java file, including local files and external library source code (jdt:// or jrt:// URIs). The Java Jdtls MCP server exposes 15 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Java Jdtls server.
Java Jdtls tools are categorised as Read (11), Write (2), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept