Skip to main content
Glama

set_payload_generator

Generate social engineering payloads (PowerShell, HTA) for authorized penetration tests and red team engagements. Requires explicit confirmation and only works with authorized targets.

Instructions

Generate a social engineering payload for use in authorized campaigns.

WARNING: This is a destructive operation that generates executable payloads intended for authorized penetration tests and red team engagements ONLY. Requires explicit human confirmation before execution.

Uses SET's "Create a Payload and Listener" module via seautomate to generate a payload that, when executed by a target, will establish a reverse connection to the operator's listener.

Supported payload types: - powershell_alphanumeric: PowerShell shellcode injector (alphanumeric) - powershell_reverse: PowerShell reverse shell - hta: HTML Application (HTA) attack

Args: payload_type: Type of payload to generate. One of: powershell_alphanumeric, powershell_reverse, hta. lhost: Attacker's IP address that the payload will connect back to. lport: TCP port on lhost that the listener will bind to. timeout: Execution timeout in seconds (default: from config).

Returns: Dict with tool name, payload_type, lhost, lport, returncode, output (truncated to 5000 chars), errors (truncated to 2000 chars), and success flag.

Note: REQUIRES HUMAN CONFIRMATION. Generates executable attack payloads. Only execute with explicit written authorization from the target organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lhostYes
lportYes
timeoutNo
payload_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: it is destructive, generates executable payloads, requires explicit human confirmation, and returns specific truncation behavior for output/errors. This goes beyond minimal disclosure and addresses safety and authorization requirements.

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 well-structured with clear sections (warning, usage, supported types, args, returns, note) and front-loaded with the critical warning. It is slightly verbose but every section earns its place; a bit of trimming could make it more concise.

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

Completeness5/5

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

Given the tool's complexity and danger, the description is complete: it explains purpose, parameters, return value structure, and critical warnings. The output schema exists to cover return details, so the description's coverage is more than sufficient.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully by explaining each parameter in detail: payload_type enumerates supported values, lhost/lport describe their role, and timeout notes the default. This adds meaning beyond the raw schema fields.

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: 'Generate a social engineering payload' via SET's 'Create a Payload and Listener' module. It distinguishes itself from sibling tools like set_credential_harvester and set_qrcode_attack by focusing on payload generation for reverse connections.

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

Usage Guidelines4/5

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

The description clearly states when to use it: authorized penetration tests and red team engagements only. It emphasizes the requirement for human confirmation and written authorization. However, it does not explicitly contrast with alternative tools or state when NOT to use it, though the context is clear.

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/rfunix/tengu'

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