defense_mgmt

Defense: tool checks, workflows, change history, posture, scheduled audits, remediation, reports

SERVERDefense SOURCEdefense-mcp-server

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/defense/defense-mgmt.md

WHAT IT DOES

What defense_mgmt does on Defense

AI agents use defense_mgmt to create or update resources in Defense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defense environment.

Parameter	Type	Required	Description
`gate`	boolean	—	Audit gate mode: block if required tools missing
`name`	string	—	Audit job name ([a-zA-Z0-9_-] only)
`tool`	string	—	Filter by tool name
`force`	boolean	—	Force reinstall even if installed
`limit`	number	—	Maximum entries to return
`lines`	number	—	Number of recent log lines
`since`	string	—	Filter by date, e.g. 'today', '2024-01-01'
`action`	string	Yes	Defense management action
`format`	string	—	Report output format
`source`	string	—	Source of findings to remediate
`command`	string	—	Audit command from approved allowlist
`dry_run`	boolean	—	Preview without executing

Parameters from the server's own tool schema.

RISK

Why defense_mgmt is rated Medium

While the tool includes read components (checks, reports, posture visibility), the presence of remediation capabilities and change tracking indicates it performs reversible modifications to system configurations and security policies. This is Write-category behavior rather than Read-only, as it alters defensive system states.

From the tool's definition Tool description mentions "change history", "remediation", and "scheduled audits" — these are write operations that modify system state. The term "remediation" specifically indicates the tool makes corrective changes to security posture.

Risk signalsHigh parameter count (26 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs defense_mgmt safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For defense_mgmt, this is the rule to start with:

defense_mgmt Rate-limited

defense_mgmt stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "defense_mgmt": {
      "limits": [
        {
          "counter": "defense_mgmt_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Defense, apply this rule, and every defense_mgmt call is checked against it from then on.

FAQ

Questions about defense_mgmt

What does the defense_mgmt tool do? +

Defense: tool checks, workflows, change history, posture, scheduled audits, remediation, reports. It is categorised as a Write tool in the Defense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does defense_mgmt accept? +

defense_mgmt accepts 12 parameters: gate, name, tool, force, limit, lines, since, action, format, source, command, dry_run. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on defense_mgmt? +

Register the Defense MCP server in PolicyLayer and add a rule for defense_mgmt: 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 Defense. Nothing to install.

What risk level is defense_mgmt? +

defense_mgmt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit defense_mgmt? +

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

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

defense_mgmt is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Defense, and thousands of servers like it.

This server

All 31 Defense tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →