Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_audit_events

Read-only

Retrieve audit trail events for a Sophos Central tenant, including admin actions and policy changes. Filter by date, category, or user for targeted security monitoring.

Instructions

List audit trail events for a Sophos Central tenant. Covers admin actions, policy changes, user logins, and configuration modifications. Supports filtering by date range, category, user, and cursor-based pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor returned by a previous response to fetch the next page of results
to_dateNoReturn events at or before this ISO 8601 UTC timestamp (e.g. '2024-01-31T23:59:59.999Z')
user_idNoFilter events to those performed by a specific user ID
categoryNoFilter by audit event category (e.g. 'policy', 'endpoint', 'iam', 'firewall')
from_dateNoReturn events at or after this ISO 8601 UTC timestamp (e.g. '2024-01-01T00:00:00.000Z')
page_sizeNoNumber of events per page (1–100, default 50)
tenant_idYesTenant UUID
max_resultsNoMaximum total number of audit events to return across all pages (used to cap large result sets)
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by detailing the scope (admin actions, policy changes, etc.) and pagination support. No contradictions. Does not mention rate limits or authentication specifics, but these are implicit.

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?

Two sentences: first states verb+resource, second lists covered events and capabilities. No redundant information, front-loaded with core purpose, every sentence adds value.

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 tool with no output schema, the description adequately covers event types and filtering options. Could mention pagination cursor behavior, but 'cursor-based pagination' implies the response includes cursor for next page. With 8 parameters, completeness is good.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all 8 parameters. The description restates the filtering capabilities (date range, category, user, pagination) but does not add new meaning beyond what the schema provides. Baseline of 3 is appropriate.

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?

Description clearly states the tool lists audit trail events for a Sophos Central tenant, specifies covered event types (admin actions, policy changes, user logins, configuration modifications), and mentions filtering and pagination. This distinguishes it from siblings like sophos_get_audit_event (single event) and sophos_search_alerts (alerts vs audit).

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?

Description implies use for listing audit events with filters and pagination, but does not explicitly state when to use this tool versus alternatives like sophos_search_alerts or sophos_get_siem_events. No exclusion criteria or when-not-to-use guidance is provided.

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/rijul170/sophos-central-mcp'

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