Skip to main content
Glama
ESET-MCP

ESET-MCP

by maciekaz

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ESET_USERYesAPI user (required for env auth mode)
ESET_REGIONNoCloud region: eu, de, us, ca, jpneu
ESET_PASSWORDYesAPI password (required for env auth mode)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
eset_searchA

Case-insensitive substring search across devices, users, policies and groups. Returns matching items with their UUIDs and which field matched. Use this instead of list_* + manual filtering when you have a name fragment (e.g. 'jeff', 'laptop-23', 'finance').

device_full_profileA

One call → device record + recent detections + vulnerabilities + recent scans. Use when answering 'what do you know about this machine'. Each sub-section degrades gracefully if the tenant lacks a module.

incident_full_contextA

One call → incident + comments + related detections + affected devices. Detections and devices are capped at 10 each to stay within rate limits; the response carries a 'truncated' flag if more exist.

latest_detectionsA

Newest detections in a time window, sorted by occurTime descending. Use this - NOT raw incident_detections__list_detections_* - when answering 'what's the latest detection / what happened recently'. The raw list endpoints do NOT sort by date, so a first-page sort silently returns stale rows. This composite does v2→v1 fallback, paginates the time window, and sorts locally.

app_executables__list_executablesC

List executables - (GET /v1/executables) - List all the executables.

app_executables__get_executableC

Get executable - (GET /v1/executables/{executableUuid}) - Get details of a specific executable.

task_device_tasks__list_tasksC

List tasks - (GET /v1/device_tasks) - List all device tasks matching criteria.

task_device_tasks__get_taskB

Get task - (GET /v1/device_tasks/{taskUuid}) - Get the task entity.

For a complete history, call ListTaskRuns().

task_device_tasks__list_task_runsA

List task runs - (GET /v1/device_tasks/{taskUuid}/runs) - List task history - all the runs of the task.

For the sake of forensics, the [task run]s are listed collectively, not as children of their parent task. Information about task runs might easily survive their parent task.

Info: Modeled based on Jobs: Executions and results with ESET specific vocabulary.

device_device_groups__list_groupsB

List all device groups - (GET /v1/device_groups) - Hierarchy can be reconstructed from the returned device_groups.

device_device_groups__list_member_devicesB

List devices in device group - (GET /v1/device_groups/{groupUuid}/devices) - Return the list of devices within a [device group].

Info: The lifecycle of membership and devices are uncorrelated: a device can be a member of many arbitrary groups without a device entity knowing that. This is also supported by the fact that some systems responsible for the device-group membership are autonomous and do not need to update the device state to remember membership.

As a

device_devices__list_devicesC

List managed devices - (GET /v1/devices) - List all the managed [device]s.

device_devices__get_deviceC

Get device details - (GET /v1/devices/{deviceUuid}) - Get details of a [device].

device_devices__batch_get_devicesB

Get batch of devices - (GET /v1/devices:batchGet) - Retrieves a specific set of devices at a consistent time point.

Info: Modeled after Batch methods: Get

iam_permissions__list_permissionsB

List permissions - (GET /v2/permissions) - List all possible permissions.

iam_identity_provider__list_rolesC

List roles - (GET /v2/role-assignments) - List [role]s of [subject]s.

Info: Not only Users are [subject]s, but anything that can have roles attached. For example, Devices.

Info: Modeled after List role assignments.

Might be filtered by the specified [subject] or [scope]s.

If the filters are left empty, all the roles availa

incident_detections__list_detections_v1C

List detections - (GET /v1/detections) - Return a list of all the [detection]s matching criteria.

incident_detections__get_detection_v1C

GET /v1/detections/{detectionUuid} - (GET /v1/detections/{detectionUuid})

incident_detection_groups__list_detection_groupsB

List detection groups - (GET /v2/detection-groups) - Return a list of all the [detection group]s matching criteria.

incident_detection_groups__get_detection_groupB

Get detection group - (GET /v2/detection-groups/{detectionGroupUuid}) - Get details about a detection group.

incident_detections__list_detections_v2C

List detections - (GET /v2/detections) - Return a list of all the [detection]s matching criteria.

incident_detections__get_detection_v2C

Get detection - (GET /v2/detections/{detectionUuid}) - Get detection.

incident_edr_rule_exclusions__list_edr_rule_exclusionsC

List EDR rule exclusions - (GET /v2/edr-rule-exclusions) - List [EDR rule exclusion]s matching criteria.

incident_edr_rule_exclusions__get_edr_rule_exclusionB

Get EDR rule exclusion - (GET /v2/edr-rule-exclusions/{exclusionUuid}) - Get details of an [EDR rule exclusion].

incident_edr_rules__list_edr_rulesC

List EDR rules - (GET /v2/edr-rules) - List [EDR rule]s matching the criteria.

incident_edr_rules__get_edr_ruleC

Get EDR rule - (GET /v2/edr-rules/{ruleUuid}) - Get [EDR rule] details.

incident_incidents__list_incidentsC

List incidents - (GET /v2/incidents) - Returns a list of incidents matching the filter. The list is ordered according to order_by.

incident_incidents__get_incidentC

Get incident - (GET /v2/incidents/{incidentUuid}) - Get details of a specific incident.

incident_incident_comments__list_incident_commentsA

List incident comments - (GET /v2/incidents/{incidentUuid}/comments) - List Comments that are accessible to the caller. The user must always specify the uuid of an Incident in arguments; therefore, the list is always provided only for one Incident.

Comments are ordered by create_time.

incident_incident_comments__get_incident_commentB

Get incident comment - (GET /v2/incidents/{incidentUuid}/comments/{commentUuid}) - Get an Incident Comment.

Preconditions:

  • incident_uuid must point to an existing incident.

installer_installers__list_installersC

List installers - (GET /v1/installers) - List all installers available to the caller.

installer_installers__get_installerC

Get installer - (GET /v1/installers/{installerUuid}) - Get details of the requested [installer].

nap_network_access_configurator__list_ip_setsB

List IP sets - (GET /v1/policies/{policyUuid}/ip-sets) - List all IP sets.

nap_network_access_configurator__get_ip_setC

Get IP set - (GET /v1/policies/{policyUuid}/ip-sets/{ipSetUuid}) - Get details about an IP set.

patch_patch_management__list_recent_application_patching_detailsA

List recent application patching details - (GET /v1/application-patching-processes/recent/details) - List the patching details of all application patching attempts performed recently (within the last few days).

The list might be empty if no application patching has been performed recently. Stale data (that is, not recent) is removed from the list over the course of several days.

patch_unpatched_devices__list_device_patchesB

List device patches - (GET /v1/device-patches) - If the same application, package or operating system is unpatched on multiple devices, the collection would contain entities for each device and patch individually.

The list may be empty if no patches for any device are found.

patch_patch_management__list_device_patching_detailsB

List patching details - (GET /v1/patching-process-details) - History is pruned repeatedly to prevent database flooding. Entries from at least the previous 30 days should be available at any time.

policy_policies__list_policiesB

List policies - (GET /v2/policies) - List all the policies accessible to the caller (based on the token).

policy_policies__get_policyC

Get policy - (GET /v2/policies/{policyUuid}) - Get policy details.

policy_policy_assignments__list_policy_assignmentsC

List policy assignments - (GET /v2/policy-assignments) - List all the policy assignments available to the caller.

policy_policy_assignments__get_policy_assignmentB

Get policy assignment - (GET /v2/policy-assignments/{assignmentUuid}) - Get details of the given policy assignment.

quarantine_quarantined_objects__list_quarantined_objectsC

List quarantined objects - (GET /v1/quarantined-objects) - List all quarantined objects matching the criteria in the filter.

quarantine_quarantined_objects__get_quarantined_objects_countC

Get quarantined objects count - (GET /v1/quarantined-objects/count) - Get the count of quarantined objects matching the criteria.

quarantine_quarantined_objects__get_quarantined_objectC

Get quarantined object - (GET /v1/quarantined-objects/{objectUuid}) - Get a quarantined object.

user_users__list_usersC

List users - (GET /v1/users) - Retrieves a list of users, optionally filtered by certain criteria defined in the user filter.

user_users__get_userA

Get user - (GET /v1/users/{userUuid}) - Retrieves the details of a specific user based on their unique identifier.

vuln_vulnerable_devices__list_device_os_vulnerabilitiesA

List device operating system vulnerabilities - (GET /v1/device-os-vulnerabilities) - List vulnerabilities of the operating system of the given device.

Note: Besides vulnerabilities of the Linux kernel, there are also some "core packages" whose vulnerabilities are treated as operating system vulnerabilities. For example: glibc, systemd, etc.

Such vulnerabilities are reported twice, once as an operating system vulnerability and once as a package vulnerability.

vuln_vulnerable_devices__list_device_vulnerabilitiesA

List device vulnerabilities - (GET /v1/device-vulnerabilities) - List device vulnerabilities where the vulnerabilities fit the criteria from the request.

Each vulnerability is treated individually; that is, if the device has multiple vulnerabilities, it will be listed multiple times.

vuln_vulnerability_management__list_recent_scan_detailsA

List recent scan details - (GET /v1/scans/recent) - List the scan details of all vulnerability scan attempts performed recently (within the last few days).

The list might be empty if no vulnerability scans have been performed recently. Stale data (that is, not recent) is removed from the list over the course of several days.

vuln_vulnerable_devices__list_vulnerable_devicesB

List vulnerable devices - (GET /v1/vulnerable-devices) - List vulnerable devices matching the criteria from the request.

Even if a device has multiple vulnerabilities, it will be listed only once.

wap_web_address_rules_configurator__list_web_address_rulesC

GET /v2/policies/{policyUuid}/web-address-rules - (GET /v2/policies/{policyUuid}/web-address-rules)

Prompts

Interactive templates invoked by user choice

NameDescription
audit_inactive_devicesList devices that have not checked in for X days - offboarding candidates.
vulnerability_reportBuild a CVE report: which devices have unpatched vulnerabilities, sorted by severity.
incident_triageShow open incidents + related detections. Suggest priorities.

Resources

Contextual data attached and managed by the client

NameDescription
ESET MCP mode (RO/RW)Current server mode - independent of the API account's permissions.
ESET regionAPI region (eu/de/us/ca/jpn). Only meaningful for cloud deployments.
ESET deployment kindPer-request: 'cloud' (ESET Connect API) or 'onprem' (customer-hosted ESET PROTECT console). In basic-auth mode an X-ESET-Server-URL header switches the request to on-prem.
Tools catalogList of all tools with RO/RW split and mapping to ESET endpoints.
ESET API rate limits10 req/s per credential/IP. Bursts subject to the Fair Use Policy.

TDQS

C2.8/5.0

Scored across 51 tools

Disambiguation3/5

Most resources have a clean list/get split, but there are near-duplicate pairs: incident_detections__list_detections_v1 and _v2, plus a third composite latest_detections that explicitly tells the agent not to use the raw list endpoints. Similar overlap exists between device_devices__list_devices, eset_search, and device_full_profile. The descriptions do steer the agent, but the versioned twins and raw-vs-composite overlap create real misselection risk.

Naming Consistency4/5

The bulk of the surface follows a predictable `<domain>_<resource>__<verb>_<noun>` snake_case pattern (list_incidents, get_device, list_quarantined_objects). Four composite convenience tools (eset_search, device_full_profile, incident_full_context, latest_detections) break the verb_noun convention with bare noun phrases, but they are few and clearly purposeful. Minor deviation, not chaotic.

Tool Count2/5

51 tools is heavy for a single MCP surface, and the bulk is read-only list/get boilerplate spanning ~12 sub-domains (incidents, devices, policies, patches, vulns, quarantine, IAM, NAP, WAP). Several slots are spent on redundant v1/v2 detection endpoints and overlapping composite wrappers. Trimming the versioned duplicates and folding some list/get pairs would make this far more usable.

Completeness3/5

Read coverage is genuinely broad — incidents, detections, devices, groups, policies, tasks, patches, vulnerabilities, quarantine, users, installers — with sensible count and history endpoints. However, the surface is entirely GET-only: no incident resolution/update, no comment creation (list/get only), no policy assignment writes, no task creation, and no quarantine release/remediation actions. For an EDR/incident response domain, those missing mutations are notable gaps that would dead-end many agent workflows.

Maintenance

ActivityMaintained
ResponsivenessOutdated data