Get a structured summary of a Java class including its annotations, dependencies, and methods.
AI agents call summarize_class to retrieve information from Spring Api Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static analysis and retrieval of class metadata from an already-cloned Spring Boot codebase. It queries existing code structure without executing code, modifying files, or triggering external operations. This is a read-only operation fitting the 'Read' category for retrieving data with no side effects.
From the tool's definition Tool description states it 'Get[s] a structured summary' of Java class information including annotations, dependencies, and methods. This is purely informational retrieval with no modification, execution, or side effects.
Attacks that exploit this kind of access
Get a structured summary of a Java class including its annotations, dependencies, and methods. It is categorised as a Read tool in the Spring Api Intel MCP Server, which means it retrieves data without modifying state.
Register the Spring Api Intel MCP server in PolicyLayer and add a rule for summarize_class: 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 Spring Api Intel. Nothing to install.
summarize_class 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 summarize_class 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 summarize_class. 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.
summarize_class is provided by the Spring Api Intel MCP server (mparth14/spring-api-intel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →