Skip to main content
Glama
BigfootBytes

threatlocker-mcp-server

by BigfootBytes

ThreatLocker Reports

reports
Read-onlyIdempotent

List available queries and fetch aggregated security data from ThreatLocker. Run pre-built or custom views to support compliance, audits, and external analysis.

Instructions

Query and run ThreatLocker reports.

Access pre-built and custom reports configured in the ThreatLocker portal. Reports provide aggregated views of security data across your organization.

Common workflows:

  • List all available reports: action=list

  • Run a specific report: action=get_data, reportId="..." (get IDs from list action first)

  • Review security posture: list reports, then run relevant compliance or audit reports

  • Export data for external analysis: run a report and process the returned data

Permissions: View Reports. Key response fields: reportId, name, description, reportData (dynamic columns per report type).

Related tools: action_log (raw audit events), system_audit (portal audit trail), computers (device inventory)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYeslist=show available reports, get_data=run report and get results
endDateNoEnd of the report window (ISO 8601 UTC).
reportIdNoReport GUID (required for get_data action). Find via list action first.
startDateNoStart of the report window (ISO 8601 UTC). Omit to use the report default window.
fetchAllPagesNoFetch all pages automatically (max 10 pages). Default: false (single page).
offsetInMinutesNoTimezone offset in minutes for date bucketing (e.g. -300 for UTC-5). Default: 0 (UTC).
response_formatNoOutput format: markdown (default, human-readable) or json (structured)markdown
includeChildOrganizationsNoInclude child organizations in the report (default: false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse data — shape varies by action
errorNo
successYes
paginationNo
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false; the description adds that reports are aggregated views and requires 'View Reports' permission, plus notes reportData is dynamic. No contradiction exists, and the added context about permission and aggregation goes beyond what annotations alone convey.

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 front-loaded with a one-sentence purpose, then uses compact bullet-style workflows. Every section earns its place, though 'Export data for external analysis' is somewhat obvious; still, clarity and structure are strong.

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?

With an output schema present and annotations covering safety, the description supplies the remaining selection context: permissions, related tools, key response fields, and planned workflows. An agent can navigate list/get_data and know when to choose a sibling tool. Complete for this complexity.

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?

All parameters are described in the schema (100% coverage), so the baseline is 3. The description's workflows add meaning by showing how action and reportId relate (list first, then get_data) and indicating the report window defaults and output format, going slightly 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 opens with 'Query and run ThreatLocker reports,' a specific verb+resource combination, and clarifies it covers pre-built and custom reports. It distinguishes from siblings via the 'Related tools' line and the aggregation focus, so an agent can tell reports from raw audit or device inventory tools.

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?

The 'Common workflows' section explicitly maps actions to tasks (list, get_data, export) and instructs to get reportId from the list action first. It lists related tools like action_log and system_audit for raw events/trail, implying this tool is for aggregated views, though it never explicitly states when not to use this tool.

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

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/BigfootBytes/threatlocker-mcp-server'

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