AI agents invoke scan_file_cdr to trigger actions in Threat Zone MCP Server. 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.
The tool name suggests it performs a CDR (Content Disarm and Reconstruction) scan on a file, which involves executing analysis/processing operations. Given the server context of malware analysis and sandbox execution, this tool likely submits a file for active scanning/processing. The description is empty, lowering confidence.
From the tool's definition Tool name 'scan_file_cdr' on a server described as providing 'malware analysis capabilities', 'sandbox execution', and 'threat intelligence retrieval'. CDR likely stands for Content Disarm and Reconstruction.
Documented attack patterns abuse exactly the kind of access scan_file_cdr gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threat Zone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_file_cdr:
{
"version": "1",
"default": "deny",
"tools": {
"scan_file_cdr": {
"limits": [
{
"counter": "scan_file_cdr_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}scan_file_cdr 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.
scan_file_cdr. It is categorised as a Execute tool in the Threat Zone MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Threat Zone MCP Server MCP server in PolicyLayer and add a rule for scan_file_cdr: 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 Threat Zone MCP Server. Nothing to install.
scan_file_cdr 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 scan_file_cdr 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 scan_file_cdr. 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.
scan_file_cdr is provided by the Threat Zone MCP Server MCP server (threat-zone/threatzonemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threat Zone MCP Server, 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.
31 Threat Zone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.