HexStrike AI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_statusC | Fast core health, worker readiness, active engagement scope, and capability summary. |
| capabilities_searchC | Find typed adapters and general capabilities. execution.host runs installed tools and scripts without registration; tools.inventory discovers server executables. |
| capabilities_describeB | Return operation schemas, supported versions, informational risk labels, and examples. Risk labels do not restrict execution. |
| engagement_manageC | Inspect, create, update, or revoke an engagement scope, port/protocol rules, rate/timeout budgets, and worker target. Risk labels do not restrict execution; max_risk_level is a legacy compatibility field. |
| action_prepareC | Validate a capability-specific argument object against its schema and return an immutable plan and approval grant. |
| job_startC | Start an authorized plan (via plan_id) OR directly prepare-and-start a capability (via capability_id + arguments) with optional idempotency key. |
| job_statusB | Query bounded job status, structured output, findings, and streaming events by job_id and cursor. |
| job_cancelA | Cancel a running job (or all active jobs via cancel_all=True) and terminate its OS process group. |
| evidence_readC | Paginated, redacted access to raw evidence artifacts by evidence_id or job_id. |
| memory_queryC | Bounded, engagement-scoped retrieval from local temporal memory and promoted lessons. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The job lifecycle tools are distinct, but action_prepare overlaps heavily with job_start, which can itself prepare-and-start a capability from capability_id + arguments, leaving two paths to the same end state. engagement_manage also multiplexes inspect/create/update/revoke behind one name, so its invocation semantics are less predictable than the single-purpose job_* tools.
Most names follow a resource_action pattern (job_start, job_status, job_cancel, evidence_read, memory_query, capabilities_search), with system_status and action_prepare as the only deviations. The convention is readable and predictable, but 'action_prepare' uses a vague resource noun and breaks the otherwise consistent scheme.
Ten tools is well-scoped for a security engagement orchestration server: discovery, planning, execution, monitoring, evidence, and memory each get representation. No obvious filler tools, and no critical concern is absent from the surface for count reasons.
The lifecycle is largely closed: discover capabilities, prepare a plan, start, poll, cancel, and read evidence plus memory. Minor gaps remain — there is no job enumeration tool (only cancel_all as a workaround) and no explicit approval/rejection operation for the approval grant produced by action_prepare, which may force agents into awkward paths.