Skip to main content
Glama
Sign In
Mythic MCP

Mythic MCP

by johanrobbenites
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

execute_mimikatz

Run mimikatz with custom arguments on an agent to retrieve output, enabling credential dumping and Active Directory reconnaissance.

Instructions

Runs mimikatz with the provided arguments, returning the output.

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": {
      "agent_id": "<agent_id>",
      "mimikatz_arguments": "<mimikatz_arguments>"
    },
    "name": "execute_mimikatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
mimikatz_argumentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It only states that mimikatz runs and output is returned, omitting critical details like potential credential dumping, administrative requirements, security risks, or side effects. This is a significant gap for a sensitive tool.

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

Conciseness4/5

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

The description is a single, clear sentence with no unnecessary words. It is appropriately concise, though the brevity sacrifices content quality in other dimensions.

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 and sensitivity of mimikatz, the description is severely incomplete. It lacks information about where the tool runs (agent_id), what mimikatz does, expected output format, or any warnings, making it insufficient for safe and correct invocation.

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 description coverage is 0%, and the description adds no meaning beyond the parameter names. It vaguely references 'provided arguments' but does not explain agent_id or the expected format of mimikatz_arguments, leaving the agent without guidance for filling parameters correctly.

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 runs mimikatz with provided arguments and returns output. The verb 'Runs' and specific resource 'mimikatz' distinguish it from sibling tools like run_shell_command or execute_powershell, which are generic execution tools.

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?

The description provides no guidance on when to use this tool versus alternatives such as run_shell_command or execute_powershell. It does not mention any prerequisites, exclusions, or preferred scenarios, leaving the agent without context for tool selection.

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

Deploy Server

Other Tools