loot_list

List collected loot/exfiltrated data

SERVERClaude C2 SOURCE0xyg3n/claude-c2

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/0xyg3n-claude-c2/loot-list.md

WHAT IT DOES

What loot_list does on Claude C2

AI agents call loot_list to retrieve information from Claude C2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why loot_list is rated Low

While the tool itself performs a read operation (listing/retrieval with no side effects), the context is highly concerning: it operates within a server designed for 'command and control of remote systems,' has sibling tools for security bypasses (amsi_bypass, bypassuac, defender_exclude), credential access (browser_creds), and the term 'loot/exfiltrated data' indicates it accesses information illicitly gathered from…

From the tool's definition Tool name is 'loot_list' and description states it will 'List collected loot/exfiltrated data' — the function is to retrieve and display previously collected or exfiltrated information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs loot_list safely

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

loot_list Allowed

loot_list 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": {
    "loot_list": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every loot_list call is checked against it from then on.

FAQ

Questions about loot_list

What does the loot_list tool do? +

List collected loot/exfiltrated data. It is categorised as a Read tool in the Claude C2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on loot_list? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for loot_list: 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 Claude C2. Nothing to install.

What risk level is loot_list? +

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

Can I rate-limit loot_list? +

Yes. Add a rate_limit block to the loot_list 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 loot_list completely? +

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

loot_list is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools →

Across the catalogue

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

Guides

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