AI agents invoke nodejsscan_scan to trigger actions in SAST MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the server context, this tool executes a static analysis security scan (NodeJsScan) against Node.js codebases. The description is empty, so confidence is reduced, but sibling tools like bandit_scan, checkov_scan, brakeman_scan confirm the pattern of running security scanning tools. Executing a scanner triggers external processes and analyzes code, placing it in the Execute category.
From the tool's definition Tool name 'nodejsscan_scan' implies running a Node.js static security scanner; the server description states it integrates 15+ SAST tools and supports automated vulnerability scanning through natural language commands.
Documented attack patterns abuse exactly the kind of access nodejsscan_scan 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 nodejsscan_scan:
{
"version": "1",
"default": "deny",
"tools": {
"nodejsscan_scan": {
"limits": [
{
"counter": "nodejsscan_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nodejsscan_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
nodejsscan_scan. It is categorised as a Execute tool in the SAST MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SAST MCP Server MCP server in PolicyLayer and add a rule for nodejsscan_scan: 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.
nodejsscan_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the nodejsscan_scan 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 nodejsscan_scan. 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.
nodejsscan_scan 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.