AI agents call code_read to retrieve information from Kali-Mcp-Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries file content without modifying, deleting, or executing anything. It is a straightforward read operation. Even in a security toolkit context, reading files is the lowest-risk activity. Severity is low because the impact is confined to information disclosure, and the blast radius of misuse is limited to accessing files already present in the workspace.
From the tool's definition Tool name is 'code_read' and description states it 'Read[s] file content from the workspace' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access code_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali-Mcp-Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for code_read:
{
"version": "1",
"default": "deny",
"tools": {
"code_read": {}
}
} code_read is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read file content from the workspace. It is categorised as a Read tool in the Kali-Mcp-Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for code_read: 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-Mcp-Toolkit. Nothing to install.
code_read 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 code_read 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 code_read. 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.
code_read is provided by the Kali-Mcp-Toolkit MCP server (trymonoly/kali-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali-Mcp-Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Kali-Mcp-Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.