提交文件分析：上传文件进行沙箱分析，支持PE、Office、PDF、Script等文件类型
AI agents invoke file_upload to trigger actions in ThreatMCP. 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.
This tool uploads files to an external sandbox for execution and analysis. Submitting files (especially PE executables, scripts) to a sandbox triggers external execution of potentially arbitrary code in a remote environment. The action is not purely a read — it causes an external system to execute/analyze the file, which constitutes triggering external operations.
From the tool's definition 上传文件进行沙箱分析，支持PE、Office、PDF、Script等文件类型 (Upload file for sandbox analysis, supports PE, Office, PDF, Script file types)
Documented attack patterns abuse exactly the kind of access file_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThreatMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for file_upload:
{
"version": "1",
"default": "deny",
"tools": {
"file_upload": {
"limits": [
{
"counter": "file_upload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}file_upload stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
提交文件分析：上传文件进行沙箱分析，支持PE、Office、PDF、Script等文件类型. It is categorised as a Execute tool in the ThreatMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Threat MCP server in PolicyLayer and add a rule for file_upload: 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 ThreatMCP. Nothing to install.
file_upload 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 file_upload 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 file_upload. 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.
file_upload is provided by the Threat MCP server (naxg/threatmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThreatMCP, 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.
15 ThreatMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.