Given a SARIF violation from a scan, provide root-cause analysis and step-by-step remediation guidance. Pass the full violation object or just the ruleId and file path.
AI agents call explain_violation to retrieve information from Squirex Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool analyzes and returns explanatory information about security violations. It accepts input parameters (violation object, ruleId, file path) and generates guidance output. No side effects occur: it does not create, modify, delete data, execute code, or trigger external operations. The tool is purely informational, making it a Read operation with low blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'provide[s] root-cause analysis and step-by-step remediation guidance' given a violation object or identifiers.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Given a SARIF violation from a scan, provide root-cause analysis and step-by-step remediation guidance. Pass the full violation object or just the ruleId and file path. It is categorised as a Read tool in the Squirex Dev MCP Server, which means it retrieves data without modifying state.
Register the Squirex Dev MCP server in PolicyLayer and add a rule for explain_violation: 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 Squirex Dev. Nothing to install.
explain_violation 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 explain_violation 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 explain_violation. 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.
explain_violation is provided by the Squirex Dev MCP server (squirex-dev/squirex-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 →