Skip to main content
Glama

vulnerability_scan_check

Assess vulnerability scanning compliance against PCI DSS ASV requirements. Input scan dates and results to identify gaps and generate compliance documentation.

Instructions

Evaluate vulnerability scanning compliance per PCI DSS ASV requirements.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.

When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.

Args: last_external_scan_date (str): The last external scan date to analyze or process. last_internal_scan_date (str): The last internal scan date to analyze or process. external_scan_passed (bool): The external scan passed to analyze or process. internal_scan_passed (bool): The internal scan passed to analyze or process. asv_vendor (str): The asv vendor to analyze or process. quarterly_scans (bool): The quarterly scans to analyze or process. scan_after_changes (bool): The scan after changes to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
last_external_scan_dateNo
last_internal_scan_dateNo
external_scan_passedNo
internal_scan_passedNo
asv_vendorNo
quarterly_scansNo
scan_after_changesNo
callerNo
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool() decorated function that implements the vulnerability_scan_check tool. It evaluates PCI DSS vulnerability scanning compliance (requirements 11.3, 11.3.1, 11.3.2, 11.3.1.3), checking external/internal scan dates, ASV vendor, scan pass status, quarterly schedule, and post-change scanning. Returns JSON with compliance status and any issues found.
    @mcp.tool()
    def vulnerability_scan_check(
        last_external_scan_date: str = "",
        last_internal_scan_date: str = "",
        external_scan_passed: bool = False,
        internal_scan_passed: bool = False,
        asv_vendor: str = "",
        quarterly_scans: bool = False,
        scan_after_changes: bool = False,
        caller: str = "",
        api_key: str = "",
    ) -> str:
        """Evaluate vulnerability scanning compliance per PCI DSS ASV requirements.
    
        Behavior:
            This tool is read-only and stateless — it produces analysis output
            without modifying any external systems, databases, or files.
            Safe to call repeatedly with identical inputs (idempotent).
            Free tier: 10/day rate limit. Pro tier: unlimited.
            No authentication required for basic usage.
    
        When to use:
            Use this tool when you need to assess, audit, or verify compliance
            requirements. Ideal for gap analysis, readiness checks, and generating
            compliance documentation.
    
        When NOT to use:
            Do not use as a substitute for qualified legal counsel. This tool
            provides technical compliance guidance, not legal advice.
    
        Args:
            last_external_scan_date (str): The last external scan date to analyze or process.
            last_internal_scan_date (str): The last internal scan date to analyze or process.
            external_scan_passed (bool): The external scan passed to analyze or process.
            internal_scan_passed (bool): The internal scan passed to analyze or process.
            asv_vendor (str): The asv vendor to analyze or process.
            quarterly_scans (bool): The quarterly scans to analyze or process.
            scan_after_changes (bool): The scan after changes to analyze or process.
            api_key (str): The api key to analyze or process.
    
        Behavioral Transparency:
            - Side Effects: This tool is read-only and produces no side effects. It does not modify
              any external state, databases, or files. All output is computed in-memory and returned
              directly to the caller.
            - Authentication: No authentication required for basic usage. Pro/Enterprise tiers
              require a valid MEOK API key passed via the MEOK_API_KEY environment variable.
            - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are
              included in responses (X-RateLimit-Remaining, X-RateLimit-Reset).
            - Error Handling: Returns structured error objects with 'error' key on failure.
              Never raises unhandled exceptions. Invalid inputs return descriptive validation errors.
            - Idempotency: Fully idempotent — calling with the same inputs always produces the
              same output. Safe to retry on timeout or transient failure.
            - Data Privacy: No input data is stored, logged, or transmitted to external services.
              All processing happens locally within the MCP server process.
        """
        if err := _check_auth(api_key):
            return err
        if err := _rl(caller):
            return err
    
        issues = []
        now = datetime.now()
    
        if last_external_scan_date:
            try:
                ext_date = datetime.strptime(last_external_scan_date, "%Y-%m-%d")
                days_since = (now - ext_date).days
                if days_since > 90:
                    issues.append({"issue": f"External scan {days_since} days old (>90 days)",
                                   "requirement": "11.3.2", "severity": "HIGH"})
            except ValueError:
                issues.append({"issue": "Invalid external scan date format", "severity": "LOW"})
        else:
            issues.append({"issue": "No external scan date provided", "requirement": "11.3.2", "severity": "HIGH"})
    
        if last_internal_scan_date:
            try:
                int_date = datetime.strptime(last_internal_scan_date, "%Y-%m-%d")
                days_since = (now - int_date).days
                if days_since > 90:
                    issues.append({"issue": f"Internal scan {days_since} days old (>90 days)",
                                   "requirement": "11.3.1", "severity": "HIGH"})
            except ValueError:
                issues.append({"issue": "Invalid internal scan date format", "severity": "LOW"})
        else:
            issues.append({"issue": "No internal scan date provided", "requirement": "11.3.1", "severity": "HIGH"})
    
        if not asv_vendor:
            issues.append({"issue": "No ASV vendor specified", "requirement": "11.3.2", "severity": "MEDIUM",
                            "note": "External scans must be performed by a PCI SSC Approved Scanning Vendor"})
    
        if not external_scan_passed:
            issues.append({"issue": "Last external scan did not pass", "requirement": "11.3.2", "severity": "HIGH"})
        if not internal_scan_passed:
            issues.append({"issue": "Last internal scan did not pass", "requirement": "11.3.1", "severity": "HIGH"})
        if not quarterly_scans:
            issues.append({"issue": "Quarterly scanning schedule not maintained", "requirement": "11.3", "severity": "HIGH"})
        if not scan_after_changes:
            issues.append({"issue": "Scans not performed after significant changes", "requirement": "11.3.1.3", "severity": "MEDIUM"})
    
        return json.dumps({
            "assessment_date": now.isoformat(),
            "external_scan": {"last_date": last_external_scan_date, "passed": external_scan_passed, "asv": asv_vendor},
            "internal_scan": {"last_date": last_internal_scan_date, "passed": internal_scan_passed},
            "quarterly_compliance": quarterly_scans,
            "change_scan_compliance": scan_after_changes,
            "compliance_status": "COMPLIANT" if not issues else "NON_COMPLIANT",
            "issues": issues,
        }, indent=2)
  • server.py:405-416 (registration)
    The @mcp.tool() decorator registers vulnerability_scan_check as an MCP tool. The FastMCP server instance 'mcp' is created at line 99.
    @mcp.tool()
    def vulnerability_scan_check(
        last_external_scan_date: str = "",
        last_internal_scan_date: str = "",
        external_scan_passed: bool = False,
        internal_scan_passed: bool = False,
        asv_vendor: str = "",
        quarterly_scans: bool = False,
        scan_after_changes: bool = False,
        caller: str = "",
        api_key: str = "",
    ) -> str:
  • Function signature defines the input schema: last_external_scan_date (str), last_internal_scan_date (str), external_scan_passed (bool), internal_scan_passed (bool), asv_vendor (str), quarterly_scans (bool), scan_after_changes (bool), caller (str), api_key (str). Returns a str (JSON).
    def vulnerability_scan_check(
        last_external_scan_date: str = "",
        last_internal_scan_date: str = "",
        external_scan_passed: bool = False,
        internal_scan_passed: bool = False,
        asv_vendor: str = "",
        quarterly_scans: bool = False,
        scan_after_changes: bool = False,
        caller: str = "",
        api_key: str = "",
    ) -> str:
Behavior5/5

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

With no annotations, the description carries full burden and excels. It explicitly states read-only, stateless, idempotent, safe, rate limits (free/pro), authentication needs, error handling, data privacy, and structured error responses. This is comprehensive and exceeds typical disclosure.

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

Conciseness3/5

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

The description is well-organized with sections but verbose. The 'Behavioral Transparency' section largely repeats the earlier 'Behavior' section. Parameter descriptions are repetitive and uninformative, making the text longer than needed without added value.

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

Completeness3/5

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

While behavioral transparency is thorough and output schema exists, the weak parameter semantics and generic descriptions leave a significant gap. Agents may not understand how to properly use the 9 optional parameters, harming completeness for a tool with no required inputs.

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

Parameters2/5

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

Schema description coverage is 0% (schema has no descriptions). The description's 'Args' section lists all 9 parameters but provides generic definitions ('The ... to analyze or process') that add no real meaning beyond parameter names and types. This fails to clarify role or valid values, leaving agents guessing.

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 explicitly states the tool evaluates vulnerability scanning compliance per PCI DSS ASV requirements, which is a specific verb-resource pair. It distinguishes from siblings like assess_pci_compliance (broader compliance) and network_segmentation_check (different focus).

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

Usage Guidelines4/5

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

The description includes 'When to use' and 'When NOT to use' sections, providing clear context for compliance assessment, gap analysis, and documentation generation. It warns against substituting legal advice but does not explicitly compare to sibling tools for when to choose this over others.

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/CSOAI-ORG/pci-dss-mcp'

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