> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blindsight.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Admin List Fleet Device Rules

> Every machine in the workspace carrying rules of its own.

Devices with no device-scoped rows are left out: the console already lists
the fleet, and this answers the narrower question of where somebody has
written something on top of it. The caller reads it as a map keyed by
``device_uuid``.



## OpenAPI

````yaml /api-reference/openapi.json get /api/runtime-security/agent/devices/rules
openapi: 3.1.0
info:
  title: Blindsight API
  version: 0.1.0
  description: >-
    The full Blindsight REST surface, generated from the running application.
    Replace the server host with your own deployment.


    For the Runtime Security integration surface (scan, proxy, tool calls) see
    the Runtime Security spec, which is hand written and carries worked
    examples.
servers:
  - url: https://api.your-blindsight.com
    description: Your Blindsight deployment
security: []
tags:
  - name: Authentication
  - name: Single sign-on
  - name: Social sign-in
  - name: SCIM provisioning
  - name: Projects
  - name: Datasets
  - name: Uploads and imports
  - name: Scans
  - name: Schedules
  - name: Healing
  - name: RAG corpora
  - name: Custom rules
  - name: Playground
  - name: Search and activity
  - name: Apps
  - name: Devices and agents
  - name: Discovery
  - name: DLP policy
  - name: DLP installation
  - name: Compliance
  - name: Audit trail
  - name: Reports
  - name: Export templates
  - name: Workspaces
  - name: Users
  - name: Invitations
  - name: API keys
  - name: Settings
  - name: Directory sync
  - name: Integrations
  - name: Pending actions
  - name: License
  - name: Onboarding
  - name: Support
  - name: Platform operations
  - name: Webhooks
paths:
  /api/runtime-security/agent/devices/rules:
    get:
      tags:
        - Devices and agents
      summary: Admin List Fleet Device Rules
      description: >-
        Every machine in the workspace carrying rules of its own.


        Devices with no device-scoped rows are left out: the console already
        lists

        the fleet, and this answers the narrower question of where somebody has

        written something on top of it. The caller reads it as a map keyed by

        ``device_uuid``.
      operationId: >-
        admin_list_fleet_device_rules_api_runtime_security_agent_devices_rules_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.