AI agents invoke pacu_attack 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.
The tool executes an exploitation framework (Pacu) which performs attack operations on cloud infrastructure. This is Execute category (runs code/triggers external operations) rather than merely querying, and the severity is critical due to the potential for widespread damage to AWS environments, including unauthorized access to cloud resources, data exfiltration, service disruption, and infrastructure compromise.
From the tool's definition 'Execute Pacu AWS exploitation framework' - this tool runs Pacu, an AWS exploitation framework designed to perform attacks against AWS infrastructure and services.
Attacks that exploit this kind of access
Execute Pacu AWS exploitation framework. 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 pacu_attack: 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.
pacu_attack 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 pacu_attack 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 pacu_attack. 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.
pacu_attack 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 →