Skip to main content
Glama
Bitdefender GravityZone MCP Server

Bitdefender GravityZone MCP Server

by WYRE-AI

bitdefender_list_quarantine_items

Lists quarantined files on endpoints or one machine, with threat name, file path, SHA256, endpoint details, quarantine date, and pending action status. Read-only; supports filters and pagination.

Instructions

List files quarantined on computers and virtual machines - threat name, file path, file SHA256, endpoint name/IP/ID, quarantine date and pending action status. This is the record of what the antimalware engine actually caught, including detections already cleaned. Scope to one machine with endpointId (from bitdefender_list_endpoints), or omit it for the whole network of the key's company. Needs an API key with the Quarantine API enabled. Read-only - never removes or restores a quarantined file (createRemove/createRestore quarantine tasks are excluded). Returns a paginated envelope: page/pagesCount/perPage/total/items.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bitdefender_list_quarantine_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page number (1-based). Defaults to 1.
filtersNoOptional filters; all selected filters must match. Text filters match partially; a leading * matches as a suffix (e.g. "*invoice.exe").
perPageNoItems per page (max 100). Defaults to 30.
endpointIdNoOnly items from this endpoint (ID from bitdefender_list_endpoints). Omit for the whole network.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and does so: it declares the tool read-only, states it never removes or restores, names the excluded task types, and specifies the API key permission (Quarantine API enabled) required to call it. It also describes the paginated return envelope (page/pagesCount/perPage/total/items), so the agent knows the response shape without an output schema.

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 definition is front-loaded with purpose and returned fields, then scoping, then permissions, then the safety exclusion, then the response envelope; every sentence adds distinct information. It is dense but somewhat long, with the permissions and return-envelope sentences arguably compressible, keeping it just under a 5.

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

Completeness5/5

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

For a four-parameter read tool with nested filters and no output schema, the description covers what an agent needs: scope selection, permission prerequisite, mutation exclusion, and pagination shape. Nothing required for correct invocation is missing.

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%, so the baseline is 3, and the description adds a bit beyond the schema by tying endpointId to its source tool and restating its omit-for-whole-network semantics. It does not add syntax or behavioral meaning for page/perPage/filters beyond what the schema already documents.

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 opens with a specific verb and resource (list files quarantined) and then enumerates the exact fields returned (threat name, file path, SHA256, endpoint name/IP/ID, quarantine date, action status), so the agent knows precisely what this tool yields. It also distinguishes the tool from the mutation path by noting createRemove/createRestore quarantine tasks are excluded, separating it from the sibling bitdefender_list_blocklist_items despite similar naming.

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?

It gives explicit scoping guidance: pass endpointId from bitdefender_list_endpoints for one machine, or omit it for the whole company network, and it clarifies that already-cleaned detections are included. It does not explicitly state when an agent would prefer this over the blocklist or incidents tools, so the differentiation against those siblings is left implicit rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.