list_credentials

List all stored credentials in the Cobalt Strike teamserver

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/list-credentials.md

WHAT IT DOES

What list_credentials does on Cobalt Strike MCP Server

AI agents call list_credentials to retrieve information from Cobalt Strike MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_credentials is rated Low

This tool retrieves credential data without side effects, placing it in the Read category. Severity is high because: (1) credentials are highly sensitive assets; (2) exposure of stored credentials could enable lateral movement, privilege escalation, or persistence; (3) in the context of a red team framework, this represents significant sensitive information.

From the tool's definition Tool name 'list_credentials' and description 'List all stored credentials' indicate data retrieval with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_credentials safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cobalt Strike MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_credentials, this is the rule to start with:

list_credentials Allowed

list_credentials is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_credentials": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every list_credentials call is checked against it from then on.

FAQ

Questions about list_credentials

What does the list_credentials tool do? +

List all stored credentials in the Cobalt Strike teamserver. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_credentials? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for list_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 Cobalt Strike MCP Server. Nothing to install.

What risk level is list_credentials? +

list_credentials is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_credentials? +

Yes. Add a rate_limit block to the list_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.

How do I block list_credentials completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_credentials? +

list_credentials is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 220 Cobalt Strike MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →