Manage harvested credentials in Empire
AI agents call empire_credentials to retrieve information from PowerShell Empire MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The description says 'manage harvested credentials' which could span Read (list/view credentials) to Write (add/update credentials). Given the ambiguity, the most likely primary use is reading/querying harvested credentials from the Empire credential store.
From the tool's definition 'Manage harvested credentials in Empire' — 'manage' is ambiguous but the tool name 'empire_credentials' without explicit create/delete/update verbs suggests credential store access
Attacks that exploit this kind of access
Manage harvested credentials in Empire. It is categorised as a Read tool in the PowerShell Empire MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PowerShell Empire MCP Server MCP server in PolicyLayer and add a rule for empire_credentials: 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_credentials is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the empire_credentials 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_credentials. 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_credentials 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 →