firewall_status

Get firewall status. 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/firewall-status.md

WHAT IT DOES

What firewall_status does on Claude C2

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

This is a read operation that retrieves firewall configuration state from a remote system. While it is non-destructive and non-modifying, the severity is elevated to 'medium' because firewall status information could be valuable reconnaissance data for an attacker planning network-based attacks or privilege escalation.

From the tool's definition Tool name 'firewall_status' and description 'Get firewall status' indicate a query/retrieval operation with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

firewall_status Allowed

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

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

FAQ

Questions about firewall_status

What does the firewall_status tool do? +

Get firewall status. 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 firewall_status? +

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

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

Can I rate-limit firewall_status? +

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

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

firewall_status 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_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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