Skip to main content
Glama
BigfootBytes

threatlocker-mcp-server

by BigfootBytes

ThreatLocker Network Access Policies

network_access_policies

Query and manage ThreatLocker network access control policies, defining firewall rules for endpoints to control application connections by IP, port, and domain.

Instructions

Query ThreatLocker network access control policies.

Network access policies define firewall rules for endpoints — controlling which applications can make or receive network connections, and to which destinations (IPs, ports, domains).

Common workflows:

  • List all network access policies: action=list

  • Search by name: action=list, searchText="RPC"

  • Filter by computer group: action=list, appliesToId="group-id"

  • Get policy details by ID: action=get, networkAccessPolicyId="..."

Pitfalls:

  • Network Control has no Global policy level (unlike application control).

  • Tag-based rules need the tag label + id resolved via the tags tool (dropdown); parent-org tags use the "ParentOrg\TagName" format.

  • direction: 1=Inbound, 2=Outbound; policyActionId: 1=Permit, 2=Deny.

Permissions: Edit Network Control Policies, View Network Control Policies. Pagination: list action is paginated (use fetchAllPages=true to auto-fetch all pages). Key response fields: networkAccessPolicyId, name, computerGroupName, isEnabled, applicationName.

Related tools: policies (application control policies), computer_groups (where policy applies), tags (network tags used in policies)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPolicy name (required for create).
portsNoPort entries, e.g. ["20-25","3389"] (create).
actionYesget=single policy by ID, list=search/list network access policies, create=create a network control policy (deploy afterwards)
statusNo1=Active, 3=Inactive (default: 1).
allPortsNoMatch any port (create).
pageSizeNoResults per page (default: 25, max: 500)
protocolNo1=TCP, 2=UDP, 3=Both (default: 3).
directionNo1=Inbound, 2=Outbound (required for create).
allSourcesNoMatch any source (create).
pageNumberNoPage number (default: 1)
searchTextNoSearch text to filter policies
appliesToIdNoComputer group GUID to filter by. Find via computer_groups first.
fetchAllPagesNoFetch all pages automatically (max 10 pages). Default: false (single page).
policyActionIdNo1=Permit, 2=Deny (required for create).
allDestinationsNoMatch any destination (create).
computerGroupIdNoOrg/group/computer GUID the policy applies to (required for create). No Global level in Network Control.
response_formatNoOutput format: markdown (default, human-readable) or json (structured)markdown
sourceLocationsNoSource locations (create).
destinationLocationsNoDestination locations (create).
networkAccessPolicyIdNoNetwork access policy GUID (required for get). Find via list action first.

Output Schema

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

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already signal read-write behavior (readOnlyHint=false), and the description adds useful operational context: permissions, pagination behavior, enum meanings for direction/policyActionId, and parent-org tag formatting. It does not disclose any create-side effects or deployment nuance, and the 'Query' framing downplays the mutation capability, so it is not a 5.

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?

The description is clearly organized into definition, common workflows, pitfalls, permissions, pagination, key response fields, and related tools. It is long but every section earns its place given the tool's 20-parameter, three-action surface area, and the opening sentence is direct.

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 a complex tool with 20 parameters, an output schema, and annotations, the description covers read workflows, filtering, pagination, permissions, and key pitfalls. The notable gap is that create is not represented in the common workflows or prose, leaving the mutating path to be inferred from the schema enum description alone.

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 description coverage is 100%, so the baseline is 3. The description adds genuine value beyond the schema by explaining tag label/id resolution, the 'ParentOrg\TagName' format, direction/policyActionId mappings, appliesToId lookup via computer_groups, and fetchAllPages behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the resource ('ThreatLocker network access control policies') and the primary read verb ('Query'), and it differentiates from sibling tools by noting 'Related tools: policies (application control policies)'. However, the tool's schema supports create as a first-class action, and the description's 'Query' opening plus common-workflow list only cover list/get, so the full purpose is understated.

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 gives concrete invocation patterns (action=list, searchText, appliesToId, action=get) and the pitfalls section tells agents about no-Global-level and tag-format constraints. It stops short of explicit 'use policies for application-control instead' routing, though the 'Related tools' line does clarify the sibling division.

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