Skip to main content
Glama

delete_dfw_rule

Destructive

Permanently delete a single DFW rule from its parent security policy. Removal is irreversible and takes effect on the NSX data plane immediately.

Instructions

[WRITE] Permanently delete one DFW rule from its parent security policy.

Deletion is irreversible and takes effect immediately on the NSX data plane: traffic the rule matched falls through to lower-priority rules or the policy's default action. Confirm the rule_id with list_dfw_rules and check recent hits with get_dfw_rule_stats before deleting. To remove an entire policy use delete_dfw_policy (it refuses while rules remain); this tool deletes a single rule without that guard. Calls are pre-checked by the vmware-policy engine (risk level: high) and audited to ~/.vmware/audit.db; the CLI equivalent additionally requires double confirmation.

Returns {"status": "deleted", "message": ...} on success, or {"error", "hint"} on failure (e.g. rule not found, connectivity).

Args: policy_id: ID of the parent security policy (alphanumeric and hyphens), as returned by list_dfw_policies. rule_id: ID of the rule to delete within that policy, as returned by list_dfw_rules. target: Optional NSX Manager target name from config. Uses the default target if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_idYes
rule_idYes
targetNo
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds behavioral details beyond annotations: deletion is irreversible, immediate effect, traffic falls to lower-priority rules, pre-checked by vmware-policy engine (high risk), and audited. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and front-loaded: starts with core action, then consequences, related tools, return format, parameters. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a destructive tool with 3 params and no output schema: covers action, consequences, prerequisites, alternatives, error cases, parameter sources, return format, auditing, and risk level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds meaning beyond input schema: explains policy_id is from list_dfw_policies (alphanumeric and hyphens), rule_id from list_dfw_rules, target is optional from config. With 0% schema coverage, description fully compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool deletes one DFW rule from its parent security policy, using specific verb and resource. It distinguishes from sibling tools like delete_dfw_policy, which removes an entire policy but refuses while rules exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: confirm rule_id with list_dfw_rules, check hits with get_dfw_rule_stats before deleting. Contrasts with delete_dfw_policy and notes CLI double confirmation. Provides clear when-to-use and when-not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zw008/VMware-NSX-Security'

If you have feedback or need assistance with the MCP directory API, please join our Discord server