AI agents use generate_consolidated_report to create or update resources in Kali — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali environment.
An AI agent can call generate_consolidated_report faster than any human can review — one bad instruction and it creates or modifies resources in Kali by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
generate_consolidated_report. It is categorised as a Write tool in the Kali MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kali MCP server in PolicyLayer and add a rule for generate_consolidated_report: 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.
generate_consolidated_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_consolidated_report 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 generate_consolidated_report. 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.
generate_consolidated_report 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 →