Skip to main content
Glama
Faceless0x7

AdaptixC2 MCP Server

by Faceless0x7

bof_process

Enumerate processes for loaded modules, handles, and TCP connections. Freeze target processes using PPL bypass, then unfreeze them.

Instructions

Process-BOF: Process enumeration and manipulation.

findobj module List all processes that have a specific module loaded. Example: findobj module clr.dll

findobj prochandle List all processes that have a handle to the specified process. Example: findobj prochandle lsass.exe

process conn List processes with established TCP/RDP connections with detailed info. Example: process conn

procfreeze freeze Freeze a target process using PPL bypass via WerFaultSecure.exe. Example: procfreeze freeze 1234

procfreeze unfreeze Unfreeze a previously frozen process. Example: procfreeze unfreeze

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
commandYes
argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. The description mentions PPL bypass for the freeze command, disclosing a critical behavioral trait. However, it fails to cover other aspects such as permissions, side effects, or the meaning of return values, leaving gaps in transparency.

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 overly long and repetitive, with multiple similar examples. It could be significantly condensed without losing information, yet it remains verbose without clear structure.

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

Completeness2/5

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

Given the tool's complexity (multiple sub-commands) and the lack of parameter documentation, the description is incomplete. The output schema exists but is not mentioned, and the description does not clarify what the tool returns for each sub-command.

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

Parameters1/5

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

Schema coverage is 0%, and the description does not explain the three parameters (agent_id, command, args). The examples imply that command is a sub-command and args are parameters, but the format is not explicitly defined, leading to ambiguity for an AI agent.

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 lists multiple sub-commands for process enumeration and manipulation but lacks a concise, single purpose statement. It does not differentiate from sibling tools like list_processes or kill_process, making it unclear when to use this tool versus others.

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?

Examples are provided for each sub-command, but there is no explicit guidance on when to use this tool versus alternatives. The description does not state prerequisites or conditions for use, leaving the agent to infer from the examples.

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