> ## Documentation Index > Fetch the complete documentation index at: https://docs.visiqlabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Activate emergency bypass > Temporarily deactivate a single retrieval rule (a time-boxed emergency bypass). The activation is written to the audit trail. Requires permission `recall_rules:bypass`. ## OpenAPI ````yaml /api-reference/openapi.yaml post /recall/rules/{id}/bypass openapi: 3.1.0 info: title: VisIQ Governance API version: 1.0.0 description: > The VisIQ platform API for governing agentic AI. One rule engine evaluates every governed agent event against your policies and returns a decision (permit, deny, approval-required, redact, mask, or escalate), records a cryptographically-verifiable audit trail, and governs agent-to-agent delegation. All requests are authenticated with a bearer API key. Mint a key in the dashboard under **Connectors -> API Keys**; it is presented as `Authorization: Bearer vq_prod_...`. Keys are scoped: harness/agent keys reach the operational surface (evaluate, rule bundles, telemetry, record ingestion), while management keys and dashboard sessions govern rules, agents, settings, and audit reads through role-based permissions. Decision vocabularies differ per facet. Action governance emits `permit | deny | approval_required | mask`. Retrieval governance emits `allow | deny | redact | escalate`. The unified `POST /evaluate` surface projects both into a single union vocabulary (`permit | deny | approval_required | redact | escalate | mask`). contact: name: VisIQ Labs url: https://docs.visiqlabs.com servers: - url: https://api.visiqlabs.com description: Production security: - bearerAuth: [] tags: - name: Evaluation description: Per-event governance decisions for action, retrieval, and delegation. - name: Action Rules description: Manage the rules that govern agent actions (writes/tool calls). - name: Retrieval Rules description: Manage the rules that govern retrieval and context exposure. - name: Unified Rules description: Operation-native rule management across both facets in one surface. - name: Rule Bundles description: Compiled, cacheable rule bundles the SDK runtime pulls per agent. - name: Agents description: Register and manage the agents whose events you govern. - name: Human-in-the-loop description: The approval queue for events that require a human decision. - name: Settings description: Per-account governance defaults. - name: Delegation description: Govern scoped agent-to-agent hand-offs with signed grant tokens. - name: Records description: Ingest, retrieve, finalize, and verify the tamper-evident audit trail. - name: Audit Log description: Versioned, paginated read APIs over recorded decisions and events. - name: Cognition description: >- Read captured Agent Cortex cognition sessions and beats (dedicated cognition:read scope). paths: /recall/rules/{id}/bypass: parameters: - $ref: '#/components/parameters/RuleId' post: tags: - Retrieval Rules summary: Activate emergency bypass description: > Temporarily deactivate a single retrieval rule (a time-boxed emergency bypass). The activation is written to the audit trail. Requires permission `recall_rules:bypass`. operationId: activateRetrievalBypass requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/BypassActivate' example: reason: Incident INC-4821 — investigating a blocked lookup duration_minutes: 30 responses: '200': description: The rule with its bypass now active. content: application/json: schema: $ref: '#/components/schemas/RetrievalRuleDetail' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' security: - bearerAuth: [] components: parameters: RuleId: name: id in: path required: true schema: type: string format: uuid description: The rule UUID. schemas: BypassActivate: type: object required: - reason - duration_minutes properties: reason: type: string minLength: 10 description: Justification (at least 10 characters). duration_minutes: type: integer enum: - 15 - 30 - 60 - 120 description: How long the bypass stays active. RetrievalRuleDetail: type: object properties: id: type: string format: uuid name: type: string description: type: - string - 'null' rego_source: type: string natural_language: type: - string - 'null' priority: type: integer enabled: type: boolean trust_tier: type: - string - 'null' surface: type: - string - 'null' principal_exclusions: type: - array - 'null' items: type: string bypass_active: type: boolean bypass_reason: type: - string - 'null' bypass_activated_by: type: - string - 'null' bypass_activated_at: type: - string - 'null' format: date-time bypass_expires_at: type: - string - 'null' format: date-time created_at: type: string format: date-time updated_at: type: string format: date-time Error: type: object required: - error description: > The standard error envelope. `details` carries the validation issue list on 400s; authorization failures add fields such as `detail`, `requiredScopes`, or `requiredPermission`. properties: error: type: string detail: type: string code: type: string details: type: array items: type: object additionalProperties: true additionalProperties: true responses: BadRequest: description: The request was malformed or failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid request body details: - path: - agent_id message: Required Unauthorized: description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Unauthorized Forbidden: description: The key lacks the required permission or scope. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: insufficient_scope detail: This API key is not authorized for the requested operation. NotFound: description: >- The requested resource does not exist (or is not visible to this account). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Rule not found Conflict: description: The request conflicts with current state. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer description: > A VisIQ API key presented as `Authorization: Bearer vq_prod_...`. Mint keys under **Connectors -> API Keys** in the dashboard. ````