Skip to main content
Glama
malloryai

Mallory MCP Server

Official
by malloryai

get_vulnerability_configurations

Identify affected systems and versions for a specific vulnerability using CPE standards to enable targeted remediation and accurate vulnerability assessment.

Instructions

Get configuration information for a specific vulnerability

Use this tool when you need to understand exactly which systems, products, or versions are affected by a vulnerability. This information is essential for:

  • Determining if your specific product versions are vulnerable

  • Planning targeted remediation efforts

  • Conducting accurate asset vulnerability mapping

  • Filtering out false positives in vulnerability scanning

  • Understanding the scope of affected software/hardware configurations

The configuration data follows CPE (Common Platform Enumeration) standards to precisely identify affected systems.

Args: identifier (str): The unique CVE ID or UUID of the vulnerability to retrieve. Example formats: "CVE-2023-1234" or "123e4567-e89b-12d3-a456-426614174000"

Returns: Dict[str, Any]: List of vulnerable configurations for the specified vulnerability, where each configuration contains: - uuid: Unique identifier for this configuration record - cpe_id: Identifier for this CPE configuration - set_id: Identifier for the set this configuration belongs to - is_vulnerable: Boolean indicating if this configuration is vulnerable - vendor/vendor_display_name: The vendor of the affected product - product/product_display_name: The affected product name - product_type: Type of product (e.g., "application", "os") - Version range indicators: - versionStartIncluding/versionStartExcluding: Minimum affected version - versionEndIncluding/versionEndExcluding: Maximum affected version - updateStartIncluding/updateEndIncluding: Update version specifiers - Platform details: - edition: Edition of the product - language: Language of the product - sw_edition: Software edition information - target_sw: Target software environment (e.g., "wordpress") - target_hw: Target hardware environment - other: Additional targeting information - created_at/updated_at: Timestamps for record management - cve_id: The CVE identifier associated with this configuration

An empty list indicates no specific configuration information is available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes

Implementation Reference

  • The core handler function for the 'get_vulnerability_configurations' MCP tool. It is registered directly via the @mcp.tool() decorator and implements the tool logic by proxying to the MalloryAI client API. Includes comprehensive docstring serving as input/output schema documentation.
    @mcp.tool()
    @handle_api_errors
    async def get_vulnerability_configurations(
        identifier: str,
    ) -> Dict[str, Any]:
        """Get configuration information for a specific vulnerability
    
        Use this tool when you need to understand exactly which systems, products, or versions
        are affected by a vulnerability. This information is essential for:
        - Determining if your specific product versions are vulnerable
        - Planning targeted remediation efforts
        - Conducting accurate asset vulnerability mapping
        - Filtering out false positives in vulnerability scanning
        - Understanding the scope of affected software/hardware configurations
    
        The configuration data follows CPE (Common Platform Enumeration) standards to precisely
        identify affected systems.
    
        Args:
            identifier (str): The unique CVE ID or UUID of the vulnerability to retrieve.
                Example formats: "CVE-2023-1234" or "123e4567-e89b-12d3-a456-426614174000"
    
        Returns:
            Dict[str, Any]: List of vulnerable configurations for the specified vulnerability,
            where each configuration contains:
                - uuid: Unique identifier for this configuration record
                - cpe_id: Identifier for this CPE configuration
                - set_id: Identifier for the set this configuration belongs to
                - is_vulnerable: Boolean indicating if this configuration is vulnerable
                - vendor/vendor_display_name: The vendor of the affected product
                - product/product_display_name: The affected product name
                - product_type: Type of product (e.g., "application", "os")
                - Version range indicators:
                    - versionStartIncluding/versionStartExcluding: Minimum affected version
                    - versionEndIncluding/versionEndExcluding: Maximum affected version
                    - updateStartIncluding/updateEndIncluding: Update version specifiers
                - Platform details:
                    - edition: Edition of the product
                    - language: Language of the product
                    - sw_edition: Software edition information
                    - target_sw: Target software environment (e.g., "wordpress")
                    - target_hw: Target hardware environment
                    - other: Additional targeting information
                - created_at/updated_at: Timestamps for record management
                - cve_id: The CVE identifier associated with this configuration
    
            An empty list indicates no specific configuration information is available.
        """
        return await malloryai_client.vulnerabilities.get_vulnerability_configurations(
            identifier=identifier
        )
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 of behavioral disclosure. It effectively describes the tool's behavior: it retrieves configuration data following CPE standards, returns a detailed dictionary structure with specific fields, and clarifies that an empty list indicates no configuration info is available. It doesn't mention rate limits, authentication needs, or error handling, but covers core operational aspects well.

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?

The description is well-structured with clear sections (purpose, usage guidelines, parameter details, return format). It's appropriately detailed for a tool with rich output, though slightly lengthy. Every sentence adds value, such as the use cases and CPE standard mention, with no redundant information.

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 (1 parameter but detailed output) and lack of annotations/output schema, the description is highly complete. It covers purpose, usage, parameter details, and a comprehensive return structure with field explanations. The note about empty lists handling edge cases adds robustness, making it sufficient for effective tool use.

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?

The schema has 0% description coverage, so the description must fully compensate. It provides comprehensive parameter semantics: explains the 'identifier' parameter as 'The unique CVE ID or UUID of the vulnerability to retrieve', gives example formats ('CVE-2023-1234' or UUID), and clarifies its purpose. This adds significant value beyond the bare schema.

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's purpose with specific verbs ('Get configuration information') and resources ('for a specific vulnerability'), distinguishing it from siblings like 'get_vulnerabilities' (which likely lists vulnerabilities) or 'get_vulnerability_detection_signatures' (which focuses on detection). It explicitly explains what configuration information entails (affected systems, products, versions).

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 provides explicit guidance on when to use this tool ('Use this tool when you need to understand exactly which systems, products, or versions are affected by a vulnerability') and lists five specific use cases (e.g., determining if versions are vulnerable, planning remediation). It implicitly distinguishes from siblings by focusing on configuration details rather than general vulnerability info or exploitation data.

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/malloryai/mallory-mcp-server'

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