Skip to main content
Glama
CoveoSec
by CoveoSec

audits_agents_reports

Retrieve agent event reports and audit logs from Cortex XSIAM with filtering, sorting, and pagination to investigate endpoint activities.

Instructions

Get Audit Agent Report

Get agent event reports.

  • Response is concatenated using AND condition (OR is not supported).

  • Maximum result set size is 100.

  • Offset is the zero-based number of incidents from the start of the result set.

Required license: Cortex XSIAM Premium or Cortex XSIAM Enterprise or Cortex XSIAM Enterprise Plus

[POST /public_api/v1/audits/agents_reports] · Audit log

Example request body:

{
  "request_data": {
    "filters": [
      {
        "field": "trapsversion",
        "operator": "in",
        "value": [
          "<version value>",
          "<version value>"
        ]
      },
      {
        "field": "timestamp",
        "operator": "gte",
        "value": 0
      },
      {
        "field": "domain",
        "operator": "in",
        "value": [
          "WORKGROUP"
        ]
      }
    ],
    "sort": {
      "field": "timestamp",
      "keyword": "asc"
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_dataNoA dictionary containing the API request fields. An empty dictionary returns all results.
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It reveals important behaviors: responses are concatenated with AND logic (OR unsupported), max result set size is 100, offset is zero-based, and required licenses are specified. This goes well beyond a simple one-line summary.

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

Conciseness4/5

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

The description is moderately long but each section contributes: summary, behavioral constraints, license, and an example. The example is substantial but earns its place by demonstrating parameter usage. It is structured with bullets and a code block, making it scannable.

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

Completeness4/5

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

For a list/filter tool with no output schema, the description covers key request-side context: filtering semantics, limits, offsets, licensing, and an example. It does not describe the response format, but given the tool's simple query nature, the provided information is sufficient for basic invocation.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value by including a detailed example request body that shows how to construct filters and sort, illustrating the semantics of nested parameters beyond the schema's textual descriptions. This helps an agent craft valid requests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get agent event reports,' which clearly identifies the tool's function as retrieving audit/agent event reports. The resource is specific ('agent event reports'), distinguishing it from sibling tools like audits_management_logs, though no explicit comparison is made.

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

Usage Guidelines3/5

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

The description implies usage for retrieving agent event reports and includes license requirements as a prerequisite. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions like 'for management logs, use audits_management_logs.'

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/CoveoSec/xsiam-mcp'

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