Recherche dans la documentation Spring Boot avec des mots-clés
AI agents call search_spring_docs to retrieve information from Springdocs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches documentation content based on keyword input. It performs a read-only query operation against Spring documentation without creating, modifying, deleting, or executing any external systems. The blast radius of misuse is minimal—an AI could only retrieve irrelevant or excessive documentation, causing no data integrity or operational harm.
From the tool's definition Tool name 'search_spring_docs' and description 'Recherche dans la documentation Spring Boot avec des mots-clés' (search in Spring Boot documentation with keywords) indicate a search/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_spring_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Springdocs, and nothing reaches the server without passing your rules. This is the rule we recommend for search_spring_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_spring_docs": {}
}
}search_spring_docs 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.
Recherche dans la documentation Spring Boot avec des mots-clés. It is categorised as a Read tool in the Springdocs MCP Server, which means it retrieves data without modifying state.
Register the Springdocs MCP server in PolicyLayer and add a rule for search_spring_docs: 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 Springdocs. Nothing to install.
search_spring_docs 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_spring_docs 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_spring_docs. 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_spring_docs is provided by the Springdocs MCP server (tky0065/springdocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Springdocs, 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.
12 Springdocs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.