client_info

Get detailed info about a specific client

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/client-info.md

WHAT IT DOES

What client_info does on Claude C2

AI agents call client_info 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 client_info is rated Low

This is a Read operation (retrieves client data). Severity is elevated to medium because on a system control server, detailed client information could be sensitive (IP, OS, installed software, credentials in clipboard), and an AI agent misuse could expose that data to an attacker.

From the tool's definition Tool name is 'client_info' with description 'Get detailed info about a specific client' — explicitly retrieves/queries information with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs client_info 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 client_info, this is the rule to start with:

client_info Allowed

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

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 client_info call is checked against it from then on.

FAQ

Questions about client_info

What does the client_info tool do? +

Get detailed info about a specific client. 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 client_info? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for client_info: 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 client_info? +

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

Can I rate-limit client_info? +

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

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

client_info 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

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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