# start_packet_capture

A execute tool on the FortiManager MCP Server MCP server.

Agent View of the PolicyLayer registry record for `start_packet_capture`. HTML page: https://policylayer.com/tools/rstierli-fortimanager-mcp/start-packet-capture

## Facts

- Tool: `start_packet_capture`
- Server: FortiManager MCP Server (`rstierli/fortimanager-mcp`) — https://policylayer.com/tools/rstierli-fortimanager-mcp.md
- Homepage: https://github.com/rstierli/fortimanager-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "start_packet_capture",
    "arguments": {}
  }
}
```

## Why start_packet_capture is rated High

Packet capture is a network execution operation that initiates monitoring and data collection on live systems. While not destructive or financial, it triggers external operations (on Cisco modeling lab infrastructure) whose effects depend on network conditions and arguments.

From the tool's own definition: "Tool name 'start_packet_capture' combined with sibling tool 'check_packet_capture_status' indicates network packet capture initiation—an operation that executes on network infrastructure and generates side effects by intercepting and recording traffic."

## Use case

AI agents invoke start_packet_capture to trigger actions in FortiManager MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FortiManager MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_packet_capture": {
      "limits": [
        {
          "counter": "start_packet_capture_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on FortiManager MCP Server (235)

- `delete_address` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-address.md
- `delete_address_group` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-address-group.md
- `delete_antivirus_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-antivirus-profile.md
- `delete_application_list` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-application-list.md
- `delete_cli_template_group` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-cli-template-group.md
- `delete_device` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device.md
- `delete_device_dhcp_server` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-dhcp-server.md
- `delete_device_group` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-group.md
- `delete_device_interface` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-interface.md
- `delete_device_ipsec_phase1_interface` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-ipsec-phase1-interface.md
- `delete_device_ipsec_phase2_interface` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-ipsec-phase2-interface.md
- `delete_device_vap` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-vap.md
- `delete_device_wtp` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-device-wtp.md
- `delete_devices_bulk` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-devices-bulk.md
- `delete_dlp_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-dlp-profile.md
- `delete_dnsfilter_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-dnsfilter-profile.md
- `delete_firewall_policies_bulk` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-firewall-policies-bulk.md
- `delete_firewall_policy` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-firewall-policy.md
- `delete_ips_sensor` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-ips-sensor.md
- `delete_local_in_policy` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-local-in-policy.md
- `delete_local_in_policy6` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-local-in-policy6.md
- `delete_package` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-package.md
- `delete_script` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-script.md
- `delete_sdwan_template` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-sdwan-template.md
- `delete_service` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-service.md
- `delete_service_group` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-service-group.md
- `delete_ssl_ssh_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-ssl-ssh-profile.md
- `delete_task` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-task.md
- `delete_waf_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-waf-profile.md
- `delete_webfilter_profile` — Destructive — https://policylayer.com/tools/rstierli-fortimanager-mcp/delete-webfilter-profile.md
- …and 205 more: https://policylayer.com/tools/rstierli-fortimanager-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=rstierli-fortimanager-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/rstierli-fortimanager-mcp