Low Risk

summarize_scan_results

summarize_scan_results

How to control summarize_scan_results ↓

What summarize_scan_results does on SAST MCP Server

AI agents call summarize_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.

Low Risk

Why summarize_scan_results needs a policy

The tool processes and summarizes security scan findings already generated by other tools (bandit_scan, semgrep, etc.), producing a report or summary. This is a read-only aggregation operation with no side effects on systems or data. Severity is low because misuse results in presentation of false security conclusions at worst, not unauthorized access or system compromise.

From the tool's definition Tool name 'summarize_scan_results' indicates a data retrieval and summarization operation on existing scan results. No modifications, deletions, or command execution described.

Documented attack patterns abuse exactly the kind of access summarize_scan_results gives an agent:

How to control summarize_scan_results

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 summarize_scan_results:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "summarize_scan_results": {}
  }
}

summarize_scan_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SAST MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about summarize_scan_results

What does the summarize_scan_results tool do? +

summarize_scan_results. It is categorised as a Read tool in the SAST MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on summarize_scan_results? +

Register the SAST MCP Server MCP server in PolicyLayer and add a rule for summarize_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.

What risk level is summarize_scan_results? +

summarize_scan_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit summarize_scan_results? +

Yes. Add a rate_limit block to the summarize_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.

How do I block summarize_scan_results completely? +

Set action: deny in the PolicyLayer policy for summarize_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.

What MCP server provides summarize_scan_results? +

summarize_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.

Enforce policy on every SAST MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.