Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_create_user_attestation

Create a user attestation to verify suspicious activity by sending a security question to the user's mobile device and collecting their answer.

Instructions

Create a user activity attestation — push a security question to a user's Intercept X for Mobile device. Use this to verify whether suspicious activity (e.g. an unexpected login) was performed by the legitimate user. The user receives the question on their mobile device and selects an answer option. Poll the attestation status using sophos_get_user_attestation. Status values: 'pending' (awaiting response), 'completed' (user answered), 'expired' (timed out).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoSpecific fields to include in a partial response (e.g. ['id', 'status'])
optionsNoCustom answer options (max 5). If omitted, default 'yes' and 'no' options are used.
user_idYesUUID of the user to send the attestation to
referenceNoOptional caller-defined reference string returned with the attestation object (alphanumeric, commas, hyphens, slashes, colons; max 256 chars)
tenant_idYesTenant UUID
title_textYesTitle of the attestation question shown on the mobile device (default language, max 100 chars)
question_textYesThe question text shown to the user on their mobile device (max 500 chars)
timeout_in_secondsNoSeconds before the attestation expires (60–86400, default 600). After expiry the attestation becomes read-only.
title_translationsNoOptional translations for the title. Keys are RFC 4646 language tags (e.g. 'de', 'fr'), values are translated text.
question_translationsNoOptional translations for the question. Keys are RFC 4646 language tags (e.g. 'de', 'fr'), values are translated text.
Behavior4/5

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

No annotations provided, so description carries full burden. Explains the lifecycle: push question, user responds, poll status. Mentions status values and timeout. Does not disclose permissions or side effects, but adequate.

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 with clear structure: defines tool, explains use case, outlines workflow. No superfluous information. Front-loaded with purpose.

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 10 parameters including nested objects, the description covers the main purpose and lifecycle. Lacks output specification, but no output schema is provided. Sufficient for a creation tool.

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 coverage is 100%, baseline 3. Description adds value by stating default behavior for 'options' (default yes/no) and 'timeout_in_seconds' (default 600). This aids understanding beyond the schema.

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?

The description clearly states 'Create a user activity attestation' with specific verb and resource. It distinguishes from sibling tools like sophos_get_user_attestation by describing the polling flow. No ambiguity.

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

Usage Guidelines4/5

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

Describes when to use: 'to verify whether suspicious activity...was performed by the legitimate user'. Suggests polling with sophos_get_user_attestation. Lacks explicit 'when not to use', but context is sufficient.

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