Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

scan_file_sandbox_simple

Analyze files for malware by submitting them to a sandbox with default settings. This tool provides basic security scanning without advanced configuration options.

Instructions

Submit a file for simple sandbox analysis using default settings.

This is a simplified version of scan_file_sandbox with default configurations. Use scan_file_sandbox for advanced configuration options.

Args: file_path: Path to the file to analyze is_public: Whether the scan results should be public (default: False) entrypoint: File to execute within archive (if applicable) password: Password for archive files (if applicable)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
is_publicNo
entrypointNo
passwordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'scan_file_sandbox_simple' tool. Decorated with @app.tool for FastMCP registration. Implements simplified sandbox file scanning by delegating to the full scan_file_sandbox function with auto_config enabled.
    @app.tool
    async def scan_file_sandbox_simple(
        file_path: str, 
        is_public: bool = False, 
        entrypoint: Optional[str] = None, 
        password: Optional[str] = None
    ) -> Dict[str, Any]:
        """
        Submit a file for simple sandbox analysis using default settings.
        
        This is a simplified version of scan_file_sandbox with default configurations.
        Use scan_file_sandbox for advanced configuration options.
        
        Args:
            file_path: Path to the file to analyze
            is_public: Whether the scan results should be public (default: False)
            entrypoint: File to execute within archive (if applicable)
            password: Password for archive files (if applicable)
        """
        return await scan_file_sandbox(
            file_path=file_path,
            is_public=is_public,
            entrypoint=entrypoint,
            password=password,
            auto_config=True  # Use automatic configuration for simplicity
        )
  • Supporting advanced sandbox scanning function used by scan_file_sandbox_simple. Handles the core logic of file upload and configuration for ThreatZone API sandbox analysis. Also registered as its own tool.
    @app.tool
    async def scan_file_sandbox(
        file_path: str, 
        is_public: bool = False, 
        entrypoint: Optional[str] = None, 
        password: Optional[str] = None,
        environment: str = "w10_x64",
        timeout: int = 180,
        work_path: str = "desktop",
        mouse_simulation: bool = True,
        https_inspection: bool = False,
        internet_connection: bool = False,
        raw_logs: bool = False,
        snapshot: bool = False,
        sleep_evasion: bool = False,
        smart_tracing: bool = False,
        dump_collector: bool = False,
        open_in_browser: bool = False,
        extension_check: bool = True,
        modules: Optional[List[str]] = None,
        auto_config: bool = False
    ) -> Dict[str, Any]:
        """
        Submit a file for advanced sandbox analysis with detailed configuration.
        
        Args:
            file_path: Path to the file to analyze
            is_public: Whether the scan results should be public (default: False)
            entrypoint: File to execute within archive (if applicable)
            password: Password for archive files (if applicable)
            environment: Analysis environment - w7_x64, w10_x64, w11_x64, macos, android, linux (default: w10_x64)
            timeout: Analysis timeout in seconds - 60, 120, 180, 240, 300 (default: 180)
            work_path: Working directory - desktop, root, %AppData%, windows, temp (default: desktop)
            mouse_simulation: Enable mouse simulation (default: True)
            https_inspection: Enable HTTPS inspection (default: False)
            internet_connection: Enable internet connection (default: False)
            raw_logs: Include raw logs (default: False)
            snapshot: Take VM snapshots (default: False)
            sleep_evasion: Enable sleep evasion techniques (default: False)
            smart_tracing: Enable smart tracing (default: False)
            dump_collector: Enable dump collection (default: False)
            open_in_browser: Open files in browser (default: False)
            extension_check: Perform extension check (default: True)
            modules: Analysis modules to use, e.g., ["csi", "cdr"] (default: None)
            auto_config: Use automatic configuration (default: False)
        """
        if not Path(file_path).exists():
            raise ThreatZoneError(f"File not found: {file_path}")
        
        # Build the analyze configuration
        analyze_config = [
            {"metafieldId": "environment", "value": environment},
            {"metafieldId": "private", "value": not is_public},
            {"metafieldId": "timeout", "value": timeout},
            {"metafieldId": "work_path", "value": work_path},
            {"metafieldId": "mouse_simulation", "value": mouse_simulation},
            {"metafieldId": "https_inspection", "value": https_inspection},
            {"metafieldId": "internet_connection", "value": internet_connection},
            {"metafieldId": "raw_logs", "value": raw_logs},
            {"metafieldId": "snapshot", "value": snapshot},
            {"metafieldId": "sleep_evasion", "value": sleep_evasion},
            {"metafieldId": "smart_tracing", "value": smart_tracing},
            {"metafieldId": "dump_collector", "value": dump_collector},
            {"metafieldId": "open_in_browser", "value": open_in_browser}
        ]
        
        # Prepare form data
        data = {
            "analyzeConfig": json.dumps(analyze_config),
            "extensionCheck": str(extension_check).lower()
        }
        
        if entrypoint:
            data["entrypoint"] = entrypoint
        if password:
            data["password"] = password
        if modules:
            data["modules"] = ",".join(modules)
        
        # Build URL with auto parameter
        url = f"/public-api/scan/sandbox?auto={str(auto_config).lower()}"
        
        files = {"file": open(file_path, "rb")}
        try:
            return await get_client().post(url, data=data, files=files)
        finally:
            files["file"].close()
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only partially delivers. It mentions 'default settings' and 'simplified version' which gives some behavioral context, but doesn't disclose important traits like whether this is a read/write operation, authentication requirements, rate limits, or what happens after submission. The description adds value but leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly structured and concise: a clear purpose statement, usage guidance, and parameter explanations in a well-organized format. Every sentence earns its place with no wasted words, and the information is front-loaded appropriately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (file analysis with 4 parameters), no annotations, but with an output schema present, the description is reasonably complete. It covers purpose, differentiation, parameters, and usage guidance. The output schema handles return values, so the description doesn't need to explain those. The main gap is lack of behavioral disclosure beyond what's provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates well by explaining all 4 parameters in the Args section. It provides semantic meaning for each parameter beyond just their names, including default values and conditional usage ('if applicable'). However, it doesn't elaborate on format requirements or constraints beyond the basics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Submit a file for simple sandbox analysis') and resource ('file'), distinguishing it from the sibling 'scan_file_sandbox' by specifying it uses 'default settings' and is a 'simplified version'. This provides clear differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides usage guidance: 'Use scan_file_sandbox for advanced configuration options' and identifies this as the 'simplified version' for default settings. This gives clear when-to-use and when-not-to-use criteria with named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/threat-zone/threatzonemcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server