Find all classes in the codebase that reference a given class name.
AI agents call find_usages 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.
This is a static analysis query that searches for references within a codebase. It performs a read-only retrieval of information about class dependencies and usage patterns. No code is executed, no data is modified, and no side effects occur. The tool operates on analyzed codebase metadata to answer a natural language query, consistent with the server's purpose of static analysis without running the application.
From the tool's definition Tool name 'find_usages' and description 'Find all classes in the codebase that reference a given class name' indicates a search/query operation that retrieves information about code references without modifying any data.
Attacks that exploit this kind of access
Find all classes in the codebase that reference a given class name. 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 find_usages: 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.
find_usages 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 find_usages 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 find_usages. 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.
find_usages 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.
find_usages is one line of Spring Api Intel's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →