Skip to main content
Glama
BigfootBytes

threatlocker-mcp-server

by BigfootBytes

ThreatLocker Saved Searches

saved_searches
Destructive

List, save, and delete saved Unified Audit/investigation searches for a ThreatLocker page. Reproduce search parameters with valid JSON and human-readable labels to organize audit workflows.

Instructions

Manage saved Unified Audit / investigation searches.

A saved search has two parts: searchData (the reproducible parameters, as JSON) and saveParameters (a human-readable label). saveSearchPageId selects which page the search belongs to (valid values 1-10; e.g. the Unified Audit page).

Common workflows:

  • List saved searches for a page: action=list, saveSearchPageId=

  • Save a search: action_log build_search_string (→ saveParameters label) → action=insert, saveSearchId=, saveSearchPageId=, organizationId="...", searchName="...", saveParameters="Any Deny", searchData={the search params object}

  • Delete a saved search: action=delete, saveSearchId="..."

Pitfalls:

  • searchData is REQUIRED and must be valid JSON (object or JSON string) — the API deserializes it and returns an opaque 500 if it is missing or malformed. (Verified live 2026-07-06.)

  • saveParameters is the display label from action_log build_search_string (e.g. "Any Deny").

  • saveSearchPageId must be a valid page type (1-10); 0/other values return "Page type wasn't found".

  • insert requires you to supply a fresh saveSearchId GUID.

Permissions: View Unified Audit.

Related tools: action_log (build_search_string produces saveParameters)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYeslist=saved searches for a page, insert=save a new search, delete=delete a saved search
datetimeNoOptional created timestamp (UTC).
usernameNoOptional owner username.
searchDataNoREQUIRED for insert: the search parameters that make the search reproducible, as a JSON object or JSON string. The API deserializes this server-side, so it MUST be valid JSON (missing/non-JSON => opaque 500).
searchNameNoDisplay name of the saved search (required for insert).
searchCountNoOptional usage counter.
saveSearchIdNoSaved-search GUID. For insert, supply a NEW GUID; for delete, the existing one.
fetchAllPagesNoFetch all pages automatically (max 10 pages). Default: false (single page).
organizationIdNoOrganization GUID (required for insert).
saveParametersNoHuman-readable search label from action_log build_search_string, e.g. "Any Deny" (required for insert). Round-trip verbatim.
response_formatNoOutput format: markdown (default, human-readable) or json (structured)markdown
saveSearchPageIdNoThe page/feature the saved searches belong to (required for list and insert; e.g. the Unified Audit page id).

Output Schema

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

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing verified failure modes (opaque 500 on malformed searchData, 'Page type wasn't found' for invalid saveSearchPageId), requiring a fresh GUID for insert, and noting the round-trip requirement for saveParameters. This gives an agent concrete expectations for what happens and what to avoid.

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 well-structured with workflows, pitfalls, permissions, and related tools. There is minor redundancy (saveParameters is described in both the intro and the pitfalls), but the extra length is justified by the complexity and risk of the operations.

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, the return format does not need to be explained. All operational prerequisites, failure modes, required parameters per action, and related tools are covered, making the description complete for an agent to select and invoke this tool correctly.

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

Parameters5/5

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

Although the schema already covers all 12 parameters, the description adds critical operational semantics: valid saveSearchPageId range (1-10), the requirement to generate a new saveSearchId for insert, that searchData must be valid JSON and is server-side deserialized, and that saveParameters comes from action_log. These details materially improve correct invocation.

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 states a specific resource ('saved Unified Audit / investigation searches') and the three concrete operations (list, insert, delete) that make up 'manage'. It distinguishes the tool from siblings by naming the action_log relationship and by scoping the resource to saved searches rather than audits or policies.

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

Usage Guidelines5/5

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

The description gives explicit workflows for list, save, and delete, including exact parameter mappings for each workflow. It also names the related tool (action_log) and states when to use it (build_search_string produces saveParameters), plus the required permission.

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