AI agents call set_info to retrieve information from Kali without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves informational content about SET capabilities — a Read operation with no direct side effects. However, the context (a Kali Linux pen-testing server with offensive tools like Hydra, Metasploit, SQLMap) means this information could be used to plan social engineering attacks.
From the tool's definition 'Get information about Social Engineering Toolkit capabilities and attack vectors'
Attacks that exploit this kind of access
Get information about Social Engineering Toolkit capabilities and attack vectors. It is categorised as a Read tool in the Kali MCP Server, which means it retrieves data without modifying state.
Register the Kali MCP server in PolicyLayer and add a rule for set_info: 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.
set_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the set_info 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 set_info. 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.
set_info is provided by the Kali MCP server (rangta10/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 →