This record as markdown: /tools/0xyg3n-claude-c2/defender-status.md
What defender_status does on Claude C2
AI agents call defender_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.
Why defender_status is rated Low
This tool only reads and reports the current status of Windows Defender (enabled/disabled, threat levels, etc.). It has no side effects, does not execute code, modify data, or delete resources. The verb 'Get' confirms it is a retrieval operation. Severity is low because status information is non-sensitive operational data that an agent could misuse only to gather reconnaissance, not to cause direct harm.
From the tool's definition Tool name is 'defender_status' and description states 'Get Defender status' — a query operation that retrieves information about Windows Defender state without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs defender_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 defender_status, this is the rule to start with:
defender_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every defender_status call is checked against it from then on.
Questions about defender_status
Get Defender 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.
Register the Claude C2 MCP server in PolicyLayer and add a rule for defender_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.
defender_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the defender_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.
Set action: deny in the PolicyLayer policy for defender_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.
defender_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.
More on Claude C2, and thousands of servers like it.
This server
Across the catalogue