Skip to main content
Glama
joesecurity

JoeSandboxMCP

Official
by joesecurity

get_domain_info

Extract domains and detection indicators from completed Joe Sandbox analyses to identify malicious activity, including resolved IP addresses and threat classifications.

Instructions

Retrieve domains in a completed analysis, along with their associated detection indicators.

This tool extracts domains gathered by the sandbox engine and returns relevant context such as resolved IP address, activity status, and detection metadata.
Optional filtering parameters allow control over the inclusion of domains and indicators based on their assessed severity.

Args:
    webid (required): The submission ID of the analysis.
    run (default: 0): Index of the sandbox run to inspect (from the `runs` array in analysis info).
    only_malicious_elements (default: True): If True, returns only domains explicitly classified as malicious by the sandbox engine.
    only_malicious_indicators (default: True): If True, limits the returned indicators to those considered clearly malicious by the detection logic.
        This excludes low-impact behavioral signals and focuses on indicators with a high likelihood of malicious intent or confirmed threat classification.
        If False, all observed indicators are included regardless of their severity.

Returns:
    A dictionary containing a list of malicious domains. Each entry includes:
      - name: The domain name.
      - ip: The resolved IP address, if available.
      - active: Whether the domain was reachable during analysis.
      - malicious: 'true' for domains classified as malicious
      - indicators: List of triggered detection rules, if any. Each entry includes:
          - desc: Description of the matched detection rule.
          - data: Matched content or signature.
          - source: The detection subsystem responsible (e.g. Suricata, Sigma, global traffic etc.).
            - impact: Either "high" or "low", indicating the severity or confidence of the detection.  
                High-impact indicators are strongly associated with malicious behavior or confirmed threats.  
                Low-impact indicators reflect general behavior or environmental traits that may not be malicious on their own.
Notes:
    - Empty Array returned if no domain was gathered during the analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webidYes
runNo
only_malicious_elementsNo
only_malicious_indicatorsNo
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behaviors: it extracts domains gathered by the sandbox engine, returns empty arrays when no domains were gathered, explains the filtering logic for malicious elements and indicators, and describes the return structure. However, it doesn't mention rate limits, authentication requirements, or potential errors.

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

Conciseness4/5

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

Well-structured with clear sections (description, args, returns, notes) but somewhat verbose in the parameter explanations. The 'Returns' section could be more concise, and some sentences repeat information. Overall efficient but with minor redundancy.

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

Completeness5/5

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

Given the complexity (4 parameters, no annotations, no output schema), the description provides excellent completeness: explains purpose, parameters, return structure with nested objects, filtering behavior, edge cases (empty arrays), and includes helpful notes about detection subsystems and impact levels. Covers all essential aspects for a domain retrieval tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed semantics for all 4 parameters: explains webid as submission ID, run as sandbox run index, and gives comprehensive explanations of the two boolean filters including their default values and the practical implications of True/False settings.

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 tool retrieves domains from a completed analysis with their detection indicators. It specifies the resource (domains in analysis), the verb (retrieve/extract), and distinguishes from siblings by focusing specifically on domain information rather than files, IPs, URLs, or other analysis components.

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

Usage Guidelines3/5

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

The description implies usage context (completed analysis with sandbox engine data) but doesn't explicitly state when to use this tool versus alternatives like get_ip_info or get_url_info. It mentions filtering capabilities but doesn't provide guidance on tool selection among the sibling analysis tools.

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/joesecurity/joesandboxMCP'

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