Skip to main content
Glama

manage_firewall_policy

Destructive

Create, update, delete, or reorder firewall policies to control traffic between zones. Policy order determines the first match; verify order after changes.

Instructions

Create, update, delete, or reorder firewall policies. Policies define traffic rules between zone pairs. CREATE requires: enabled, name, action, source (with zoneId), destination (with zoneId), ipProtocolScope, loggingEnabled. REORDER: pass data as { policyIds: ['id1', 'id2', ...] } to set evaluation order. CRITICAL: Policy order matters — first match wins. Always verify order after changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform
policyIdNoPolicy ID (required for update/delete)
enabledNo
nameNoPolicy name. Convention: '{action}-{src}-to-{dst}', e.g. 'allow-trusted-to-iot', 'block-guest-to-private'
descriptionNoHuman-readable description of what this policy does and why
policyActionNoWhat to do with matched traffic
sourceNoWhere traffic originates
destinationNoWhere traffic is going
ipProtocolScopeNoIP protocol version to match. Default: IPV4_AND_IPV6
loggingEnabledNoEnable syslog for matched traffic — recommended for deny rules
policyIdsNoOrdered list of policy IDs for reorder action
Behavior4/5

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

Adds significant context beyond annotations: highlights that policy order matters (first match wins), specifies required fields for CREATE, and details the reorder action format. No contradiction with annotations (destructiveHint=true, etc.).

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?

Three sentences: overview, action-specific details, critical warning. Every sentence is informative and earns its place. Front-loaded with the most important information.

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

Completeness4/5

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

Covers key complexities (order sensitivity, required fields for CREATE, reorder format). Lacks specifics on update/delete requirements, but schema provides those. No output schema, so return values are not explained; acceptable.

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

Parameters4/5

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

Schema coverage is 91% (high), so baseline is 3. The description adds value by summarizing CREATE requirements and providing a naming convention for the 'name' parameter (e.g., 'allow-trusted-to-iot'). This exceeds the baseline.

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?

Description starts with 'Create, update, delete, or reorder firewall policies,' clearly stating the verb and resource. It distinguishes itself from sibling tools like list_firewall_policies and manage_firewall_zone by specifying the operations and context.

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

Usage Guidelines4/5

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

Provides explicit guidance for CREATE (required fields) and REORDER (expected data format) and a critical warning about policy order. However, it does not compare to sibling tools or specify when to use this tool versus alternatives.

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/pproenca/unifi-mcp'

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