Search for internal company artifacts and libraries in the local Maven repository and Gradle caches by coordinate (groupId, artifactId), keyword, or class name. Use this primarily for internal company packages or to find available versions of internal projects that are locally built. Also support...
AI agents call search_artifacts 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 searches and retrieves metadata about Maven/Gradle artifacts (groupId, artifactId, versions, class names) from local caches. It performs read-only queries against indexed repositories. Even though it indexes internal company libraries, the tool itself does not execute code, modify data, delete anything, or move money. The ability to batch query does not elevate this beyond Read category.
From the tool's definition Tool description explicitly states 'Search for internal company artifacts and libraries' and 'supports searching' — these are query/retrieval operations with no modification, deletion, or execution capabilities. No side effects are mentioned.
Documented attack patterns abuse exactly the kind of access search_artifacts 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_artifacts:
{
"version": "1",
"default": "deny",
"tools": {
"search_artifacts": {}
}
}search_artifacts 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 internal company artifacts and libraries in the local Maven repository and Gradle caches by coordinate (groupId, artifactId), keyword, or class name. Use this primarily for internal company packages or to find available versions of internal projects that are locally built. Also supports searching third-party libraries in the local cache. Supports batch queries. 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_artifacts: 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_artifacts 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_artifacts 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_artifacts. 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_artifacts 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.