threatlocker-mcp

computer_update_baseline_rescan

Update baseline rescan for specified computers to refresh security baselines. Optionally enable learning mode during the rescan process.

Instructions

Update Baseline Rescan Computer

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "computer_update_baseline_rescan"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Request body.
`organization_id`	No	Override the default organization (ManagedOrganizationId header).
`override_organization_id`	No	Optional OverrideManagedOrganizationId header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 14, 2026

TDQS

D1.9/5.0

Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Update' without explaining side effects, prerequisites, or what triggers a rescan, leaving the agent uninformed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is too short to be informative; it is under-specified rather than concise. Every word should add value, but here the phrase merely echoes the tool name.

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

Completeness1/5

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

Given the complexity (nested objects, no output schema, numerous siblings), the description is severely inadequate. It omits essential details about effects, return values, and usage context.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents parameters. The description adds no additional meaning beyond the schema.

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

Purpose2/5

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

The description is a near-tautology, restating the tool name without clarifying what 'Baseline Rescan' means or distinguishing it from sibling update tools like computer_update_for_edit.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., computer_update_for_edit). The description provides zero context for decision-making.

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

Deploy Server