Analyzes PHP code for Silverstripe 6 compatibility issues. MUST be called on any generated Silverstripe PHP code before presenting to the user. Keep calling until no issues remain. Detects: - Wrong namespace imports (e.g., SilverStripe\\ORM\\ArrayList should be SilverStripe\\Model\\List\\ArrayLis...
AI agents call ss-validator 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 performs static analysis/validation of provided PHP code. It reads and inspects code to report compatibility issues but does not execute the code, modify any data, or produce side effects. It is purely a linting/analysis tool, equivalent to a read/query operation on the supplied text.
From the tool's definition Analyzes PHP code for Silverstripe 6 compatibility issues — detects wrong namespaces, old patterns, missing properties, deprecated usage
Attacks that exploit this kind of access
Analyzes PHP code for Silverstripe 6 compatibility issues. MUST be called on any generated Silverstripe PHP code before presenting to the user. Keep calling until no issues remain. Detects: - Wrong namespace imports (e.g., SilverStripe\\ORM\\ArrayList should be SilverStripe\\Model\\List\\ArrayList) - Old BuildTask patterns (run(HTTPRequest) should be execute(InputInterface, PolyOutput)) - Missing required properties (e.g., $commandName on BuildTask) - Deprecated patterns (echo in BuildTask should be $output->writeln()). 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 ss-validator: 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.
ss-validator 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 ss-validator 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 ss-validator. 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.
ss-validator 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 →