firewall-aiops

states_table

Read-only

Retrieve active pf state-table entries to inspect current firewall connections, with a limit and optional target selection for tracking or troubleshooting.

Instructions

[READ] Active pf state-table entries (connections currently tracked).

Args: top: How many state entries to return (default 100). target: Firewall target name from config; omit for the default.

Returns an envelope: {"states": [...], "returned": N, "limit": L, "truncated": bool, "total": T}. "truncated" is true when the state table holds more entries than were returned.

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": "states_table"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Aug 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and the '[READ]' tag reinforces it, so the safety profile is covered. The description goes further by disclosing the envelope shape, the truncation flag, and the default limit behavior, which is real behavioral context beyond the 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?

One-line purpose followed by a compact Args block and a single envelope sentence. Nothing is redundant and the most important scoping information is front-loaded.

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?

There is no output schema, yet the description describes the return envelope keys and the meaning of 'truncated', so the agent knows what it will get back. For a two-parameter read tool this is complete.

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 description coverage is 0%, so the description carries the full burden for both parameters. It explains 'top' (count, default 100) and that 'target' is a firewall target name from config that can be omitted for the default, which fully compensates for the undocumented schema.

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?

States a specific verb+resource: reading active pf state-table entries, with the parenthetical clarifying these are tracked connections. It distinguishes the resource from siblings like rule_states and firewall_log, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The '[READ]' tag and 'currently tracked' phrasing imply this is a live snapshot, which is useful context for when to reach for it. However, it gives no explicit when-to-use guidance relative to rule_states, kill_states, or top_talkers, and no exclusions or prerequisites.

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