Search for resources (non-class files) inside JARs, such as properties files, XML configs, or proto files.
AI agents call search_resources to retrieve information from Maven Indexer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries resource metadata from indexed JAR files without performing any modifications, reversible writes, code execution, deletions, or financial transactions. The blast radius of misuse is minimal—it can only expose information about what resources exist in local dependencies, which is typically non-sensitive metadata.
From the tool's definition Tool description explicitly states 'Search for resources' and lists examples of non-class files (properties files, XML configs, proto files) that would be queried, not modified. The parent server indexes local caches for 'search' operations.
Documented attack patterns abuse exactly the kind of access search_resources gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maven Indexer, and nothing reaches the server without passing your rules. This is the rule we recommend for search_resources:
{
"version": "1",
"default": "deny",
"tools": {
"search_resources": {}
}
}search_resources 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 resources (non-class files) inside JARs, such as properties files, XML configs, or proto files. It is categorised as a Read tool in the Maven Indexer MCP Server, which means it retrieves data without modifying state.
Register the Maven Indexer MCP server in PolicyLayer and add a rule for search_resources: 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 Indexer. Nothing to install.
search_resources 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_resources 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_resources. 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_resources is provided by the Maven Indexer MCP server (tangcent/maven-indexer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maven Indexer, 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.
6 Maven Indexer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.