List all REST endpoints in the Spring Boot project. Enriches with live Swagger/Actuator data if the app is running.
AI agents call list_endpoints 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 tool retrieves metadata about Spring Boot endpoints and enriches it with publicly-exposed Swagger/Actuator information. It performs static analysis and queries running application introspection endpoints, but does not create, modify, delete, or execute code. The blast radius of misuse is minimal — an attacker learns the API surface, which is typically already documented or discoverable.
From the tool's definition Tool description states it 'List[s] all REST endpoints' and 'enriches with live Swagger/Actuator data' — these are purely informational queries with no side effects.
Attacks that exploit this kind of access
List all REST endpoints in the Spring Boot project. Enriches with live Swagger/Actuator data if the app is running. 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 list_endpoints: 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.
list_endpoints 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 list_endpoints 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 list_endpoints. 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.
list_endpoints 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 →