Using BigFix Platform MCP Server

Example of mcp.json configuration:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bigfix-token",
      "description": "BigFix REST API token",
      "password": true
    }
  ],
  "servers": {
    "bigfixMcp": {
      "type": "http",
      "url": "https://<mcp-host>:9494",

      "headers": {
        "Authorization": "Bearer ${input:bigfix-token}",
        "X-Bes-Mcp-Read-Only": "true",
        "X-Bes-Mcp-Disable-Hitl": "false"
      }
    }
  }
}

After adding the configuration:

1. Start or reload the MCP server entry from Visual Studio Code.
2. Confirm certificate trust when prompted and ensure the listener certificate is trusted by the environment opening the connection.
3. Use MCP: List Servers to verify that the server is connected.
4. Use Copilot Chat in Agent mode so that MCP tools are available to the model.
5. For Copilot Business or Copilot Enterprise, verify that the organizational policy allows MCP server usage.

• Action Management
• Analysis Management
• Baseline Management
• Computer Management
• Fixlet Management
• Identity and access management, including identity providers, LDAP, Operators, and Roles
• Query and Session operations
• Site Management
• Task Management

The available operations and required parameters are exposed through the MCP tool schemas. Users can ask the connected AI client to describe a tool family, but product documentation should still provide examples for important operational workflows and should not rely exclusively on the model to explain the product.

The tools you can disable are the following:

• manage_bigfix_action
• manage_bigfix_analyses
• manage_bigfix_baselines
• manage_bigfix_computers
• manage_bigfix_fixlets
• manage_bigfix_idp
• manage_bigfix_ldap
• manage_bigfix_operators
• manage_bigfix_query
• manage_bigfix_roles
• manage_bigfix_session
• manage_bigfix_sites
• manage_bigfix_tasks

The MCP Server implements server-side Human-in-the-Loop enforcement for supported write-capable operations by using MCP Form Elicitation. The server stages the request before execution and asks the user to review and authorize that exact request.

The protected write flow is as follows:

1. The MCP Server classifies the requested operation as write-capable.
2. Read-only policy is applied first. If the operation is blocked, no HITL request is created.
3. The server stages an exact copy of the tool input and calculates a SHA-256 binding over the tool name, operation, and exact JSON payload bytes.
4. The approval is bound to the current MCP session and a fingerprint of the caller.
5. The server creates a pending approval with a five-minute lifetime.
6. A Form Elicitation request displays the review data and asks the user to select Allow, Deny, or Cancel.
7. Before execution, the server revalidates the session, caller, payload hash, approval state, expiry, and single-use conditions.
8. Only a valid Allow decision consumes the approval and executes the staged payload once.

The review message contains a JSON object with the following fields:

{
  "tool": "manage_bigfix_action",
  "operation": "deleteAction",
  "approval_id": "hitl_<generated-id>",
  "payload_sha256": "<sha-256>",
  "exact_staged_request": {
    "operation": "deleteAction",
    "action_id": 1123
  }
}

The SHA-256 value binds the authorization to the exact staged request bytes. Any changed request requires a new approval

Decision handling is as follows:

Client rendering and compatibility:

• The MCP Server controls the review message, the form question, the field description, the decision enum, and the default decision.
• The current form uses a string decision with Allow, Deny, and Cancel. Deny is the safe default.
• The MCP client controls native interface labels such as Submit, Respond, Accept, Decline, or Cancel. The server cannot rename client-native buttons.
• The decision explanation should appear only once, in the description beneath the form question. The review message should contain only the operation review and staged request details.
• If the client does not advertise compatible Form Elicitation support, the MCP Server blocks the protected write operation instead of continuing without approval

HITL lifecycle and execution outcomes are written to the MCP audit trail. Relevant events include: