AI agents call get_scan_statistics 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 fetch or retrieve statistics from prior scan operations. Even though the description is empty (lowering confidence slightly), the name 'get_scan_statistics' strongly suggests a read-only query operation that returns summary metrics about scan runs. No side effects, code execution, data modification, deletion, or financial impact is implied.
From the tool's definition Tool named 'get_scan_statistics' with empty description, but naming and context indicate it retrieves aggregated data about completed security scans rather than executing scans or modifying state.
Documented attack patterns abuse exactly the kind of access get_scan_statistics 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 get_scan_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_scan_statistics": {}
}
}get_scan_statistics 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.
get_scan_statistics. 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 get_scan_statistics: 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.
get_scan_statistics 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 get_scan_statistics 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 get_scan_statistics. 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.
get_scan_statistics 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.