Lists available Silverstripe 6 changelog sections. Use this to discover what documentation is available before fetching with get-documentation.
AI agents call list-sections 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 enumerates available documentation sections without modifying any data or executing code. It serves a purely informational function to help users understand what resources exist in the changelog. There are no side effects, no data mutations, and no external operations triggered. It is straightforward Read category activity with minimal risk if misused.
From the tool's definition Tool name 'list-sections' combined with description stating it 'Lists available Silverstripe 6 changelog sections' and advises using it to 'discover what documentation is available'.
Attacks that exploit this kind of access
Lists available Silverstripe 6 changelog sections. Use this to discover what documentation is available before fetching with get-documentation. 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 list-sections: 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.
list-sections 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-sections 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-sections. 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-sections 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 →