Skip to main content
Glama
Sentinel-One

Purple AI MCP Server

Official
by Sentinel-One

list_misconfigurations

Retrieve paginated misconfiguration lists with environment filtering for security audits, compliance reporting, and bulk remediation workflows.

Instructions

List misconfigurations with pagination and view filtering.

Retrieves a paginated list of misconfigurations with filtering by environment type. For advanced filtering by severity, status, compliance, etc., use search_misconfigurations instead.

Args: first: Number of misconfigurations to retrieve (1-100, default: 10). after: Pagination cursor from previous response (optional). Use pageInfo.endCursor from previous response to get next page. view_type: Environment filter with options: - "ALL": Show all misconfigurations (default) - "CLOUD": Cloud environment only - "KUBERNETES": Kubernetes environment only - "IDENTITY": Identity-related misconfigurations - "INFRASTRUCTURE_AS_CODE": IaC misconfigurations - "ADMISSION_CONTROLLER": Admission controller findings - "OFFENSIVE_SECURITY": Offensive security findings - "SECRET_SCANNING": Secret scanning findings fields: Optional JSON string containing an array of field names to return. If not specified, returns all default fields. Use minimal fields like '["id"]' when paging through intermediate results.

        Available fields:
        - Basic: "id", "externalId", "name", "severity", "status"
        - Timing: "detectedAt", "lastSeenAt", "eventTime"
        - Context: "environment", "product", "vendor", "organization"
        - Analysis: "analystVerdict", "mitigable", "exposureReason"
        - Type: "misconfigurationType"
        - IDs: "resourceUid", "exploitId", "exclusionPolicyId"
        - Nested objects (returns subfields):
          - "asset" (id, externalId, name, type, category, subcategory, privileged,
                    cloudInfo {accountId, accountName, providerName, region},
                    kubernetesInfo {cluster, namespace})
          - "scope" (account {id, name}, site {id, name}, group {id, name})
          - "assignee" (id, email, fullName)
          - "evidence" (fileName, fileType, iacFramework, ipAddress, port, subdomain)
          - "cnapp" (policy {id, version, group}, verifiedExploitable)
          - "admissionRequest" (category, resourceName, resourceNamespace, resourceType,
                               userName, userUid, userGroup)
          - "remediation" (mitigable, mitigationSteps)
          - "mitreAttacks" (techniqueId, techniqueName, techniqueUrl, tacticName, tacticUid)
        - Lists: "complianceStandards", "dataClassificationDataTypes", "dataClassificationCategories"
        - Enforcement: "enforcementAction"

        Examples:
        - Minimal for paging: '["id"]'
        - Summary view: '["id", "severity", "status", "name", "detectedAt"]'
        - With asset context: '["id", "name", "asset", "severity"]'
        - Full details: omit fields parameter or pass None

Returns: Paginated misconfiguration list in JSON format containing: - edges: Array of misconfiguration objects - pageInfo: Pagination metadata - hasNextPage: Boolean indicating more results available - hasPreviousPage: Boolean indicating previous page exists - startCursor: Cursor for first item in current page - endCursor: Cursor for last item (use for next page) - totalCount: Total number of matching misconfigurations

Common Use Cases: - Security dashboard feeds - Environment-specific security reviews - Bulk remediation workflows - Compliance reporting by scope - Cloud security posture management

Pagination Example: 1. Call with first=20 to get first 20 misconfigurations 2. Use pageInfo.endCursor as 'after' parameter for next 20 3. Continue until pageInfo.hasNextPage is false

Raises: RuntimeError: If there's an error listing misconfigurations. ValueError: If parameters are invalid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNo
afterNo
view_typeNoALL
fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description fully discloses pagination behavior, parameter effects, return values, error types, and usage patterns.

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?

Well-structured with Args, Returns, Raises, Use Cases, and Example sections. Every sentence adds value; appropriate length for the detail required.

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?

Covers all aspects: pagination, filtering, field selection, common use cases, errors, and return format. Completeness is high despite output schema existence.

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?

Adds extensive detail beyond schema: first range, after cursor usage, view_type enum values, fields JSON string with available fields and examples.

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 it lists misconfigurations with pagination and view filtering, and distinguishes from search_misconfigurations for advanced filtering.

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?

Explicitly says when to use this tool vs search_misconfigurations, provides common use cases, and includes a pagination example.

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/Sentinel-One/purple-mcp'

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