Skip to main content
Glama
FortiManager MCP Server

FortiManager MCP Server

by rstierli

list_ips_sensor_signature_overrides

Retrieve IPS sensor signature overrides and filters. Use returned IDs to remove specific overrides.

Instructions

List the signature-filter/override entries of an IPS sensor.

Each entry is either a broad filter (matched by severity/protocol/OS/...) or a specific signature override (matched by an explicit "rule" list of signature names). Use the returned "id" values with remove_ips_sensor_signature_override.

Args: adom: ADOM name sensor: IPS sensor name

Returns: dict: Entry list with keys: - status: "success" or "error" - count: Number of entries - entries: List of entry objects - message: Error message if failed

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": {
      "adom": "<adom>",
      "sensor": "<sensor>"
    },
    "name": "list_ips_sensor_signature_overrides"
  }
}

Input Schema

NameRequiredDescriptionDefault
adomYes
sensorYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the response contract: a dict with status, count, entries and an error message, plus the two distinct entry shapes. It could go further on permissions or behavior when the sensor has no overrides, but the read-only nature is unambiguous from "List" and the downstream id guidance adds real context.

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

Conciseness4/5

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

Front-loaded with the one-line purpose, then the entry-type explanation, the sibling hand-off, and compact Args/Returns blocks. Well structured, though the Returns block partly duplicates the existing output schema and could be trimmed.

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?

For a two-parameter read tool this covers what an agent needs: what is listed, what the entries mean, how to use the ids, and what comes back. The only soft spot is the shallow parameter glosses, which matters little given only two required string inputs.

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 0%, so the description must compensate. It does enumerate both parameters under Args, but the glosses ("ADOM name", "IPS sensor name") largely restate the parameter names without adding format, scope, or whether `sensor` is a name versus an object identifier — leaving a real gap for a zero-coverage schema.

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?

States a specific verb ("List") and resource ("signature-filter/override entries of an IPS sensor") and explains what an entry actually is — either a broad severity/protocol/OS filter or an explicit signature-name rule. That distinguishes it cleanly from get_ips_sensor, add_ips_sensor_signature_override and remove_ips_sensor_signature_override.

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?

Explicitly routes the agent downstream: "Use the returned 'id' values with remove_ips_sensor_signature_override," which tells the caller when this tool is a prerequisite rather than a terminal action. It stops short of stating exclusions (e.g., when to read the parent sensor instead), so it is clear context without full when/when-not coverage.

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