project_info

Get complete project structure, architecture, and codebase knowledge for making modifications

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

WHAT IT DOES

What project_info does on Claude C2

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

This tool retrieves project metadata and codebase information without side effects. However, severity is elevated to 'medium' rather than 'low' because: (1) complete codebase knowledge could expose sensitive algorithms, credentials, or architecture details that aid adversaries, and (2) the sibling tool environment includes security-bypassing tools (amsi_bypass, bypassuac, browser_creds, defender_exclude) indicating…

From the tool's definition Tool description states 'Get complete project structure, architecture, and codebase knowledge' - retrieves information about codebase without modifying it. Name 'project_info' and verb 'Get' indicate data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

project_info Allowed

project_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": {
    "project_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 project_info call is checked against it from then on.

FAQ

Questions about project_info

What does the project_info tool do? +

Get complete project structure, architecture, and codebase knowledge for making modifications. 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 project_info? +

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

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

Can I rate-limit project_info? +

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

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

project_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 →