Manage the NetExec credential database. View, search, and export stored credentials from previous scans.
AI agents call cme_creds to retrieve information from CrackMapExec MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads from a credential database storing previously captured credentials. While the action itself is non-destructive (view/search/export), the data being accessed is extremely sensitive—network credentials harvested during penetration testing. Misuse by an AI agent could expose a large number of credentials, making severity high despite being a Read operation.
From the tool's definition View, search, and export stored credentials from previous scans
Attacks that exploit this kind of access
Manage the NetExec credential database. View, search, and export stored credentials from previous scans. It is categorised as a Read tool in the CrackMapExec MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CrackMapExec MCP Server MCP server in PolicyLayer and add a rule for cme_creds: 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 CrackMapExec MCP Server. Nothing to install.
cme_creds 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 cme_creds 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 cme_creds. 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.
cme_creds is provided by the CrackMapExec MCP Server MCP server (schwarztim/sec-crackmapexec-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 →