For the complete documentation index, see llms.txt. This page is also available as Markdown.

getVibeSecPolicy

Get resolved VibeSec policy by scope, with optional user/group identifier.

Examples

query GetVibeSecPolicy($input: GetVibeSecPolicyInput!) {
  getVibeSecPolicy(input: $input) {
    governanceEnabled
    decisions {
      feature
      configured
      effective
      blockedBy
    }
    secureCoding {
      isEnabled
    }
    codeAnnotations {
      isEnabled
    }
    riskPreventionTelemetry {
      isEnabled
    }
    mcpGovernance {
      isEnabled
      defaultServerPolicy
      servers {
        id
        policy
        defaultToolPolicy
        tools {
          id
          policy
        }
      }
    }
    commandsGovernance {
      isEnabled
    }
    dependenciesGovernance {
      isEnabled
      maliciousDependencies {
        isEnabled
        rangeReachableAction
      }
      minimumVersionAge {
        isEnabled
        days
      }
    }
    mcpGuard {
      isEnabled
    }
    oxPresence {
      isEnabled
    }
    showGuidelineName {
      isEnabled
    }
    externalSaasGovernance {
      isEnabled
    }
    aiModelGovernance {
      isEnabled
    }
    promptSecretScan {
      isEnabled
      action
    }
    sensitiveDataProtection {
      isEnabled
    }
    skillsGovernance {
      isEnabled
    }
    blockMaliciousSkills {
      isEnabled
    }
  }
}

Variables

This is an example input showing all available input fields. Only fields marked as required in the schema are mandatory.

Arguments

You can use the following argument(s) to customize your getVibeSecPolicy query.

Argument
Description
Supported fields

input GetVibeSecPolicyInput! required

scope VibeSecPolicyScope! email String groupName String

Fields

Return type: VibeSecPolicyResponse!

You can use the following field(s) to specify what information your getVibeSecPolicy query will return. Please note that some fields may have their own subfields.

Field
Description
Supported fields

governanceEnabled Boolean!

Persisted master switch for governance children. When false, every governance child cascades to effective=false with blockedBy=parent.

Per-feature decision (configured vs effective + blockedBy reason) computed from the three-level AND-cascade.

feature VibeSecFeature! configured Boolean! effective Boolean! blockedBy BlockedBy

Guideline injection configuration

isEnabled Boolean

Inline security annotation configuration

isEnabled Boolean

Prevented-risk telemetry configuration

isEnabled Boolean

MCP server and tool governance configuration

isEnabled Boolean defaultServerPolicy McpGovernanceAccessMode servers [McpServerPolicyEntryResponse!]

Risky shell command governance configuration

isEnabled Boolean

Dependency governance configuration

isEnabled Boolean maliciousDependencies MaliciousDependenciesConfigResponse minimumVersionAge MinimumVersionAgeConfigResponse

Stdio MCP server guard configuration

isEnabled Boolean

"Secured by OX" session preamble configuration

isEnabled Boolean

Guideline-name visibility configuration

isEnabled Boolean

External SaaS governance configuration

isEnabled Boolean

AI model governance configuration

isEnabled Boolean

When enabled, hooks scan each prompt locally, and based on policy, either block those carrying credentials or allow them but alert on Agent Activity Log. Only the secret type and an already-masked value reach the backend.

isEnabled Boolean action PromptSecretScanAction

When enabled, only metadata is persisted to Mongo. Commands are reduced to the executable basename, file paths to the basename, and some free-text inputs are replaced with a placeholder before write.

isEnabled Boolean

Agent skill scanning configuration

isEnabled Boolean

Malicious skill blocking configuration

isEnabled Boolean

Last updated