clair_vulnerability_scan
A execute tool on the Nyxstrike MCP server.
This record as markdown: /tools/nyxstrike/clair-vulnerability-scan.md
What clair_vulnerability_scan does on Nyxstrike
AI agents invoke clair_vulnerability_scan to trigger actions in Nyxstrike. 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.
Why clair_vulnerability_scan is rated High
Clair is a well-known open-source container vulnerability scanner. In the context of an offensive security/penetration testing platform, this tool likely executes a vulnerability scan against a target system. Scanning involves active probing of external systems, making it an Execute-category action.
From the tool's definition Tool name: 'clair_vulnerability_scan'; description is empty. Server is an 'AI Powered penetration testing Platform for offensive security research' with sibling tools including payload generation, attack suites, and reconnaissance workflows.
Attacks that exploit this kind of access
The rule that runs clair_vulnerability_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clair_vulnerability_scan, this is the rule to start with:
clair_vulnerability_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every clair_vulnerability_scan call is checked against it from then on.
Questions about clair_vulnerability_scan
clair_vulnerability_scan is a execute tool on the Nyxstrike MCP server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for clair_vulnerability_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 Nyxstrike. Nothing to install.
clair_vulnerability_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 clair_vulnerability_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 clair_vulnerability_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.
clair_vulnerability_scan is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue