AI agents use target_upload_file to create or update resources in Zebbern Kali MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zebbern Kali MCP environment.
File uploads can reversibly place files on target systems and are a standard step in penetration testing exploitation chains. The tool does not irreversibly delete data (not Destructive), does not move money (not Financial), and while it may be used to stage code execution, the tool itself performs the upload action rather than executing arbitrary code (not Execute).
From the tool's definition Tool name 'target_upload_file' indicates file upload functionality. No description provided, but upload operations create or modify data on a target system.
Documented attack patterns abuse exactly the kind of access target_upload_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for target_upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"target_upload_file": {
"limits": [
{
"counter": "target_upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}target_upload_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
target_upload_file. It is categorised as a Write tool in the Zebbern Kali MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for target_upload_file: 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 Zebbern Kali MCP. Nothing to install.
target_upload_file 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 target_upload_file 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 target_upload_file. 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.
target_upload_file is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.