Search for Java classes across all jars in the repository
AI agents call search_classes 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.
This tool retrieves information about Java classes from the local Maven repository without executing code, modifying files, or causing side effects. It is a pure read operation that searches and returns results. The blast radius of misuse is minimal—an agent could discover unwanted class information but cannot alter dependencies, execute code, or delete artifacts.
From the tool's definition Tool name 'search_classes' and description 'Search for Java classes across all jars in the repository' indicate a query/search operation with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access search_classes gives an agent:
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 search_classes:
{
"version": "1",
"default": "deny",
"tools": {
"search_classes": {}
}
} search_classes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for Java classes across all jars in the repository. It is categorised as a Read tool in the Maven Decoder MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maven Decoder MCP Server MCP server in PolicyLayer and add a rule for search_classes: 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.
search_classes 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 search_classes 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 search_classes. 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.
search_classes 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.
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.