Skip to main content
Glama

List Firewalla Rules

firewalla_list_rules
Read-onlyIdempotent

Audit and review configured Firewalla network security rules to identify overly permissive settings, stale configurations, and scope mismatches for security optimization.

Instructions

Audit configured block / allow rules. Read-only — this tool does NOT pause, resume, create, or modify rules.

Use this to answer:

  • "Do I have any allow rules that bypass Firewalla's default blocks?"

  • "Which rules haven't fired in 90 days (candidates to remove)?"

  • "Are my block rules scoped to the right device/group?"

  • "Any rules with action=allow and broad scope?"

Args:

  • query (string, optional): Firewalla query-grammar filter (pass-through). Examples: action:allow, status:paused, target.type:domain.

  • response_format ('markdown' | 'json'): Output format (default: markdown).

Returns: { count: number, rules: Array<{ id: string, gid: string, action: string, // "block" | "allow" | "time_limit" | … direction?: string, // "outbound" | "inbound" | "bidirection" status?: string, // "active" | "paused" | "disabled" target: { type, value, dnsOnly?, port? }, scope?: { type?, value? }, notes?: string, hit?: { count?, lastHitTs? }, ts?: number, updateTs?: number }> }

Audit framing:

  • action=allow with scope=global → overly permissive, investigate.

  • status=paused with no notes → someone disabled a rule and didn't document why.

  • hit.count=0 & old updateTs → stale rule, candidate for removal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFirewalla query string (pass-through). See Firewalla docs for the grammar — supports filters like `device.mac:AA:BB:CC:DD:EE:FF`, `blocked:true`, `region:CN`, `ts:>1700000000`, etc. Omit to match everything.
response_formatNoOutput format. 'markdown' (default) renders human-readable audit tables. 'json' returns structured data suitable for chaining into another tool call.markdown
Behavior4/5

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

The description adds valuable behavioral context beyond the annotations. While annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, the description adds the 'audit framing' section that explains how to interpret the results for security analysis. This provides practical guidance on what patterns to look for in the returned data.

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?

The description is exceptionally well-structured and front-loaded. The first sentence establishes the core purpose, followed immediately by usage examples, parameter details, return format, and audit guidance. Every section serves a distinct purpose with zero wasted text, making it easy for an AI agent to parse and understand.

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?

Given the comprehensive annotations, detailed input schema with 100% coverage, and the rich description that includes usage examples, parameter context, return format explanation, and audit guidance, this description provides complete context for a read-only audit tool. The absence of an output schema is compensated by the detailed return structure documentation in the description.

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?

With 100% schema description coverage, the baseline would be 3. However, the description adds meaningful context by providing example queries in the 'Use this to answer' section that illustrate practical applications of the query parameter. The audit framing section also helps users understand how to interpret results based on parameter combinations.

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's purpose with specific verbs ('audit configured block/allow rules') and distinguishes it from siblings by explicitly stating what it does NOT do ('does NOT pause, resume, create, or modify rules'). This makes it immediately clear this is a read-only audit tool versus other Firewalla tools that might modify rules.

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?

The description provides excellent usage guidance with four specific example questions this tool can answer, giving concrete scenarios for when to use it. It also explicitly distinguishes from alternatives by stating what it doesn't do, helping users understand when NOT to use this tool versus modification tools.

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/productengineered/firewalla-mcp'

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