defender_exclude
Add Defender exclusion. Auto-selects client.
This record as markdown: /tools/0xyg3n-claude-c2/defender-exclude.md
What defender_exclude does on Claude C2
AI agents invoke defender_exclude to trigger actions in Claude C2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why defender_exclude is rated High
Adding a Defender exclusion disables antivirus/antimalware scanning for specified paths or processes, effectively creating a blind spot in endpoint security. This is a classic attacker technique to evade detection. Combined with sibling tools like amsi_bypass, bypassuac, and browser_creds, this tool is clearly part of an offensive/C2 toolkit.
From the tool's definition 'Add Defender exclusion' — modifies Windows Defender security configuration to exclude paths/processes from scanning, directly undermining endpoint protection
Attacks that exploit this kind of access
The rule that runs defender_exclude 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_exclude, this is the rule to start with:
defender_exclude stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_exclude call is checked against it from then on.
Questions about defender_exclude
Add Defender exclusion. Auto-selects client. It is categorised as a Execute tool in the Claude C2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude C2 MCP server in PolicyLayer and add a rule for defender_exclude: 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_exclude is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the defender_exclude 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_exclude. 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_exclude 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.
Across the catalogue