Search the SS6 changelog for specific terms. Use this when you need to find information about a specific class, method, or feature that may not be in the themed documentation sections.
AI agents call search-changelog 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 changelog documentation to find information about Silverstripe 6 classes, methods, and features. It has no side effects, cannot modify data, execute code, or trigger external operations. The worst-case misuse would be an agent reading sensitive information from the changelog, which poses minimal risk.
From the tool's definition Tool name 'search-changelog' and description explicitly states 'Search the SS6 changelog for specific terms' — a retrieval operation with no modification, execution, or deletion capability.
Attacks that exploit this kind of access
Search the SS6 changelog for specific terms. Use this when you need to find information about a specific class, method, or feature that may not be in the themed documentation 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 search-changelog: 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.
search-changelog 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-changelog 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-changelog. 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-changelog 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 →