Systems Manager

Sm Firewall Operations

sm_firewall_operations

Manage host firewall rules: check status, then add or remove allow/deny rules by protocol, port, source, and destination.

Instructions

Operations for firewall management

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "sm_firewall_operations"
  }
}

Input Schema

Name	Required	Description
`rule`	No	Structured firewall rule specification
`action`	Yes	Action to perform. Must be one of: 'get_firewall_status', 'add_firewall_rule', 'remove_firewall_rule'
`confirm`	No	Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.9Nov 3, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.",
+  "type": "boolean"
+}

First observedv2.2.5Oct 24, 2026

TDQS

C2.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about mutation risk, approval/confirm behavior, or privileges. It only faintly implies state changes via "management," which is far short of what an agent needs before adding or removing firewall rules.

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

Conciseness2/5

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

A single short phrase, but it is concise by omission rather than by editing. Nothing is front-loaded because there is essentially no content.

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

Completeness1/5

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

For a tool whose action parameter switches between reading status and destructive rule addition or removal, with no annotations and no output schema, the description omits everything an agent needs. It never explains the three actions or the confirm flag's role.

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%, so the schema already documents action, rule, and confirm in detail, establishing the baseline of 3. The description adds no meaning beyond the schema, but nothing is lost either.

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

Purpose2/5

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

"Operations for firewall management" restates the tool name and title without naming a specific verb or resource scope. It never reveals that the tool retrieves status and adds or removes rules, nor distinguishes it from siblings like sm_network_operations.

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?

No when-to-use guidance, no prerequisites, and no named alternative among the 24 sibling tools. Only the word "firewall" implies a domain, leaving the agent to guess when this tool is appropriate.

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