Skip to main content
Glama
Systems Manager

Systems Manager

Remove Firewall Rule

sm_firewall_remove_firewall_rule
DestructiveIdempotent

Removes an existing firewall rule by specifying its name, protocol, port, and action to revoke unwanted network access.

Instructions

Remove firewall rule (sm_firewall_operations). Operations for firewall management

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_firewall_remove_firewall_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleNoStructured firewall rule specification
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, covering the core safety profile. The description adds no behavioral context beyond restating the title: it does not explain what removal affects, whether confirmation is expected, or what happens when the rule is absent.

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

Conciseness3/5

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

The description is short and front-loads the operation name, which is good. However, the parenthetical module reference and "Operations for firewall management" add little value, and the second sentence does not meaningfully advance understanding of the tool.

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

Completeness3/5

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

The purpose is present, and the rich schema plus annotations compensate for many omissions, including safety hints and parameter details. Still, for a destructive firewall mutation the description itself provides no usage context, no consequence detail, and no confirmation guidance, leaving clear gaps despite the structured fields.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema documents the rule structure, rule fields, default null behavior, and the confirm flag in detail. The description adds no parameter meaning beyond the schema, so the baseline score of 3 applies.

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

Purpose4/5

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

The description states a specific verb and resource: "Remove firewall rule." That is clear enough to distinguish it from add-oriented siblings by operation, but it does not explicitly name an alternative or scope condition in the description text.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no alternative tool named. "Operations for firewall management" is a domain label, not usage guidance for choosing between removing a rule, adding one, or checking firewall status.

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

Deploy Server

Other Tools