AI agents call analyze_scan_results to retrieve information from SAST MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve and process results from previously executed scans (bandit_scan, semgrep, etc.). Analysis of scan results is a read-only operation that queries or interprets data without modifying, deleting, or executing external code. While the description is empty (lowering confidence slightly), the tool name and server context strongly suggest this is a data retrieval/interpretation function.
From the tool's definition Tool name 'analyze_scan_results' with no description provided. The verb 'analyze' indicates data retrieval and interpretation rather than modification or execution.
Documented attack patterns abuse exactly the kind of access analyze_scan_results gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAST MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_scan_results:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_scan_results": {}
}
}analyze_scan_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
analyze_scan_results. It is categorised as a Read tool in the SAST MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAST MCP Server MCP server in PolicyLayer and add a rule for analyze_scan_results: 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 SAST MCP Server. Nothing to install.
analyze_scan_results 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 analyze_scan_results 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 analyze_scan_results. 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.
analyze_scan_results is provided by the SAST MCP Server MCP server (sengtocxoen/sast-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAST MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 SAST MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.