Check the health status of the SAST Tools server.
AI agents call sast_server_health 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.
This tool queries and retrieves health/status information about the SAST server. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is purely informational and diagnostic in nature, making it a Read operation with low severity.
From the tool's definition Tool name 'sast_server_health' and description 'Check the health status of the SAST Tools server' indicate a read-only query operation that retrieves server status information without modifying, executing code, or affecting system state.
Documented attack patterns abuse exactly the kind of access sast_server_health 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 sast_server_health:
{
"version": "1",
"default": "deny",
"tools": {
"sast_server_health": {}
}
}sast_server_health 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.
Check the health status of the SAST Tools server. 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 sast_server_health: 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.
sast_server_health 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 sast_server_health 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 sast_server_health. 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.
sast_server_health 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.