Skip to main content
Glama
Sign In
PowerShell Empire MCP Server

PowerShell Empire MCP Server

by schwarztim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

empire_upload

Transfer files to a compromised agent by specifying the agent ID, remote path, and base64-encoded file content.

Instructions

Upload a file to an Empire agent

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>",
      "remote_path": "<remote_path>",
      "file_data": "<file_data>"
    },
    "name": "empire_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent ID or name
remote_pathYesPath on the target system to upload to
file_dataYesBase64-encoded file content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits like overwrite behavior, size limits, or if authentication is required. The description carries the full burden and adds little beyond the basic action.

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 concise sentence with no redundancy, but it could benefit from slightly more structure (e.g., listing parameters or expected outcomes).

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?

The tool has 3 required parameters and no output schema. The description does not mention return values or confirm upload success. For a simple file upload tool, it is adequate but could be more complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The tool description does not add meaning beyond what the schema already provides for each parameter.

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 verb 'Upload' and the resource 'file' to an 'Empire agent', distinguishing it from sibling tools like empire_download.

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?

No guidance on when to use this tool versus alternatives, such as when a file transfer is needed vs. running a module. No prerequisites or exclusions mentioned.

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