AI agents call get_spring_guide 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 Spring documentation guides. The verb 'get' and context of retrieving guide content from a documentation server are consistent with Read operations. There are no indications of data creation, modification, deletion, code execution, or financial transactions. The incomplete description ('get_spring_guide' / 'Récupère le contenu d...') does not suggest any side effects or destructive capabilities.
From the tool's definition Tool name 'get_spring_guide' and description prefix 'Récupère le contenu d' (French: 'Retrieves the content of') indicate data retrieval without modification capabilities.
Documented attack patterns abuse exactly the kind of access get_spring_guide 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 get_spring_guide:
{
"version": "1",
"default": "deny",
"tools": {
"get_spring_guide": {}
}
} get_spring_guide 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.
Récupère le contenu d. 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 get_spring_guide: 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.
get_spring_guide 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_spring_guide 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_spring_guide. 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_spring_guide 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.