installed_software

List installed programs. 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/installed-software.md

WHAT IT DOES

What installed_software does on Claude C2

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

The tool retrieves system information (installed programs inventory) with no side effects. It falls squarely into the Read category as it performs a passive enumeration/discovery operation. Severity is low because knowing installed software, while potentially useful for reconnaissance, does not directly compromise systems or data—it's foundational system query capability.

From the tool's definition Tool name is 'installed_software' and description states 'List installed programs.' This is a query operation that retrieves information about the system without modifying, deleting, or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

installed_software Allowed

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

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

FAQ

Questions about installed_software

What does the installed_software tool do? +

List installed programs. 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 installed_software? +

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

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

Can I rate-limit installed_software? +

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

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

installed_software 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

The MCP Attack Database →

Guides

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