AI agents invoke lynis_scan to trigger actions in Kali. 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.
Lynis is a system security auditing tool that scans the host OS for vulnerabilities, misconfigurations, and security issues. Executing it with arbitrary parameters against target systems constitutes running an external security tool. While it is primarily a read/audit tool, it runs on the host system with elevated privileges and its output could reveal sensitive system information.
From the tool's definition 'Execute lynis with the provided parameters' — runs the Lynis security auditing tool on the host system; server description confirms this is a Kali Linux penetration testing server supporting 'network scanning, web scanning, password attacks'
Attacks that exploit this kind of access
Execute lynis with the provided parameters. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for lynis_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 Kali. Nothing to install.
lynis_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 lynis_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 lynis_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.
lynis_scan is provided by the Kali MCP server (pentestt00ls/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →