reg_read

Read registry value. Auto-selects 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/reg-read.md

WHAT IT DOES

What reg_read does on Claude C2

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

This tool retrieves Windows registry values without any modification, deletion, or execution capabilities. It is a read-only operation with no side effects. While it may provide sensitive information (depending on what registry keys are queried), the tool itself only reads data. Severity is low because the blast radius of misuse is limited to information disclosure, not system compromise or data loss.

From the tool's definition Tool name 'reg_read' and description 'Read registry value' indicate retrieval of data with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reg_read Allowed

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

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

FAQ

Questions about reg_read

What does the reg_read tool do? +

Read registry value. Auto-selects 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 reg_read? +

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

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

Can I rate-limit reg_read? +

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

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

reg_read 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

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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