AI agents call explain_finding to retrieve information from Secscan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves explanatory data (remediation guidance) from the security scanner's knowledge base. It is a pure read operation that returns information to help users understand security findings, with no capability to modify system state, execute code, delete data, or affect financial obligations.
From the tool's definition Tool name 'explain_finding' and description 'Return remediation guidance for a finding rule_id' indicates the tool retrieves and returns informational guidance based on a rule_id parameter.
Attacks that exploit this kind of access
Return remediation guidance for a finding rule_id (from any scan result). It is categorised as a Read tool in the Secscan MCP Server, which means it retrieves data without modifying state.
Register the Secscan MCP server in PolicyLayer and add a rule for explain_finding: 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 Secscan. Nothing to install.
explain_finding 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_finding 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_finding. 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_finding is provided by the Secscan MCP server (openjkai/secscan_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 →