Retrieve the source code for a class from the local Maven/Gradle cache (containing internal company libraries). This tool identifies the containing artifact and returns the source code. It prefers actual source files but will fall back to decompilation if necessary. Use this primarily for interna...
AI agents call get_class_details 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 is a read-only operation that queries and retrieves source code from a local cache. While it provides access to internal company libraries, it performs no side effects—no data is modified, deleted, or executed. The blast radius is low: an AI agent misusing this tool could only exfiltrate source code, not corrupt systems or cause other damage. No destructive, financial, or executable operations are possible.
From the tool's definition Tool description states it will 'Retrieve the source code for a class' and 'returns the source code' with fallback to decompilation. No creation, modification, deletion, code execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access get_class_details 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 get_class_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_class_details": {}
}
}get_class_details 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.
Retrieve the source code for a class from the local Maven/Gradle cache (containing internal company libraries). This tool identifies the containing artifact and returns the source code. It prefers actual source files but will fall back to decompilation if necessary. Use this primarily for internal company libraries that are not present in the current workspace. IMPORTANT: Even if the code compiles and imports work, the source code might not be in the current workspace (it comes from a compiled internal library). Use this tool to see the actual implementation of those internal libraries. 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 get_class_details: 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.
get_class_details 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 get_class_details 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 get_class_details. 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.
get_class_details 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.