Manage Empire listeners - list, create, enable, disable, or delete listeners
AI agents call empire_listeners to permanently remove resources in PowerShell Empire MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports 'delete' operations on Empire listeners, which is irreversible. Empire is a post-exploitation C2 (Command and Control) framework; listeners are the network endpoints that receive connections from compromised agents. Deleting or disabling listeners could sever connections to active agents irreversibly.
From the tool's definition Manage Empire listeners - list, create, enable, disable, or delete listeners
Attacks that exploit this kind of access
Manage Empire listeners - list, create, enable, disable, or delete listeners. It is categorised as a Destructive tool in the PowerShell Empire MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PowerShell Empire MCP Server MCP server in PolicyLayer and add a rule for empire_listeners: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches PowerShell Empire MCP Server. Nothing to install.
empire_listeners is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the empire_listeners rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for empire_listeners. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
empire_listeners is provided by the PowerShell Empire MCP Server MCP server (schwarztim/sec-powershell-empire-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →