Fetches Silverstripe 6 changelog documentation for a specific section. Call list-sections first to see available sections.
AI agents call get-documentation to retrieve information from Silverstripe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation content from Silverstripe 6 changelog. It has no capability to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only retrieve documentation they shouldn't access, which is a low-severity information disclosure risk at most.
From the tool's definition Tool name 'get-documentation' and description 'Fetches Silverstripe 6 changelog documentation for a specific section' indicate data retrieval with no side effects. The verb 'fetches' and the action of retrieving documentation confirm read-only behavior.
Attacks that exploit this kind of access
Fetches Silverstripe 6 changelog documentation for a specific section. Call list-sections first to see available sections. It is categorised as a Read tool in the Silverstripe MCP Server, which means it retrieves data without modifying state.
Register the Silverstripe MCP server in PolicyLayer and add a rule for get-documentation: 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 Silverstripe. Nothing to install.
get-documentation 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-documentation 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-documentation. 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-documentation is provided by the Silverstripe MCP server (sandervanscheepen/silverstripe-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 →