# log_traffic_forward

A read tool on the FortiOS 7 6 X MCP Server MCP server.

Agent View of the PolicyLayer registry record for `log_traffic_forward`. HTML page: https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/log-traffic-forward

## Facts

- Tool: `log_traffic_forward`
- Server: FortiOS 7 6 X MCP Server (`paoloamato2/fortinet-mcp-server`) — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server.md
- Homepage: https://github.com/paoloamato2/fortinet-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why log_traffic_forward is rated Low

The tool name strongly implies querying or retrieving traffic forwarding logs from a Fortinet firewall. 'Log' typically indicates read-only data access, and 'traffic_forward' likely refers to inspecting traffic forwarding records or configurations. While the description is empty (lowering confidence), the naming pattern and server context suggest this retrieves information without side effects.

From the tool's own definition: "Tool name 'log_traffic_forward' suggests forwarding or retrieving traffic logs from FortiOS. The context of sibling tools being primarily read operations (get, list, profiles) and the 'log' prefix indicates data retrieval rather than modification or execution."

## Use case

AI agents call log_traffic_forward to retrieve information from FortiOS 7 6 X MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FortiOS 7 6 X MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_traffic_forward": {}
  }
}
```

## Other tools on FortiOS 7 6 X MCP Server (239)

- `cmdb_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/cmdb-delete.md
- `firewall_address_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/firewall-address-delete.md
- `firewall_addrgrp_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/firewall-addrgrp-delete.md
- `firewall_policy_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/firewall-policy-delete.md
- `firewall_vip_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/firewall-vip-delete.md
- `ips_sensor_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/ips-sensor-delete.md
- `monitor_firewall_session_close` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/monitor-firewall-session-close.md
- `monitor_vpn_ssl_delete_user` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/monitor-vpn-ssl-delete-user.md
- `router_static_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/router-static-delete.md
- `system_admin_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/system-admin-delete.md
- `system_interface_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/system-interface-delete.md
- `user_group_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/user-group-delete.md
- `user_local_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/user-local-delete.md
- `vpn_ipsec_phase1_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/vpn-ipsec-phase1-delete.md
- `vpn_ipsec_phase2_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/vpn-ipsec-phase2-delete.md
- `vpn_ssl_portal_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/vpn-ssl-portal-delete.md
- `wifi_vap_delete` — Destructive — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/wifi-vap-delete.md
- `monitor_network_ping` — Execute — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/monitor-network-ping.md
- `monitor_user_disconnect` — Execute — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/monitor-user-disconnect.md
- `wifi_wtp_deauthorize` — Execute — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/wifi-wtp-deauthorize.md
- `monitor_action` — Other — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/monitor-action.md
- `service_call` — Other — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/service-call.md
- `antivirus_profile_get` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/antivirus-profile-get.md
- `antivirus_profile_list` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/antivirus-profile-list.md
- `antivirus_settings_get` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/antivirus-settings-get.md
- `application_group_list` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/application-group-list.md
- `application_list_get` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/application-list-get.md
- `application_list_profiles` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/application-list-profiles.md
- `automation_setting_get` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/automation-setting-get.md
- `certificate_ca_list` — Read — https://policylayer.com/tools/paoloamato2-fortinet-mcp-server/certificate-ca-list.md
- …and 209 more: https://policylayer.com/tools/paoloamato2-fortinet-mcp-server.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=paoloamato2-fortinet-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/paoloamato2-fortinet-mcp-server