Skip to main content
Glama
Faceless0x7

AdaptixC2 MCP Server

by Faceless0x7

bof_sal

Perform Windows host reconnaissance and privilege escalation checks, including ARP tables, directory permissions, network connections, and system uptime.

Instructions

SAL-BOF: Situational Awareness Local — Windows host reconnaissance.

arp — List ARP table cacls — List file/directory permissions. Example: cacls C:\test.txt dir [directory] [/s] — List directory contents (recursive with /s). Example: dir C:\Users /s env — List process environment variables ipconfig — List IPv4 addresses, hostname, DNS servers listdns — List DNS cache entries and resolve them netstat — Display active network connections nslookup [-s server] [-t type] — DNS query. Example: nslookup google.com -s 8.8.8.8 -t A routeprint — List IPv4 routes uptime — Show system boot time and uptime useridletime — Show user idle time in seconds/minutes/hours/days whoami — Run whoami /all (groups, privileges, SID)

privcheck all — Run ALL privilege escalation checks privcheck alwayselevated — Check AlwaysInstallElevated registry setting privcheck autologon — Check Winlogon autologon credentials privcheck credmanager — Enumerate Windows Credential Manager privcheck hijackablepath — Check PATH for writable directories privcheck modautorun — Check for modifiable autorun executables privcheck modsvc — Check for services with modifiable DACL privcheck pshistory — Check PowerShell PSReadLine history file privcheck tokenpriv — List token privileges and highlight vulnerable ones privcheck uacstatus — Check UAC status and integrity level privcheck unattendfiles — Check for leftover unattend.xml files privcheck unquotedsvc — Check for unquoted service paths privcheck vulndrivers — Check for known vulnerable drivers (loldrivers.io)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
commandYes
argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It lists commands and their effects but does not disclose whether commands are read-only, destructive, or have side effects. While most commands appear safe, the description fails to explicitly state safety or behavioral traits.

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

Conciseness3/5

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

The description is lengthy due to listing many commands, but the list format is clear and each line adds value. However, it could be condensed for readability without losing information.

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

Completeness3/5

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

While an output schema exists, its content is not shown and the description does not describe return values. For a host reconnaissance tool with many subcommands, the description adequately guides command selection but lacks output format details, which are important for an AI agent.

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 documentation coverage is 0%, but the description compensates heavily by enumerating valid commands and their argument syntax (e.g., 'cacls <path>', 'dir [directory] [/s]'). This provides essential meaning for the 'command' and 'args' parameters beyond the generic schema.

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 clearly states the tool's purpose: 'SAL-BOF: Situational Awareness Local — Windows host reconnaissance.' It lists specific subcommands like arp, ipconfig, netstat, etc., making it distinct from sibling BOF tools that focus on AD, credentials, etc.

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

Usage Guidelines3/5

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

Usage is implied by the list of reconnaissance commands, but no explicit guidance is given on when to use this tool versus alternatives. Sibling tools have different domains (AD, credentials), but the description doesn't state 'use for local host recon' or 'not for network recon.'

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

Install Server

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/Faceless0x7/AdaptixC2-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server