Code and Change Review Assistance for Security Product Rule Operations: Tool Calling and Plugins

This category's data mainly comes from WAF, IDS, firewalls, and threat intelligence platforms. Updates occur daily or when protection events are

What Data for This Category Looks Like

This category's data mainly comes from WAF, IDS, firewalls, and threat intelligence platforms. Updates occur daily or when protection events are triggered. Daily produced documents include rule change tickets, intercept logs, false positive analysis reports, and policy rollback records. Fields typically include rule unique identifiers, interception threshold configurations, effective times, false positive trigger counts, and attack matching features. There is no unified mandatory format, and adaptation to each security product's export specifications is required.

What Constraints These Characteristics Impose on the Tool Calling and Plugins Workflow

The multi-source heterogeneous data sources require tool calling to support authentication and data fetching protocols for different security products such as WAF and IDS. It also requires adaptation to non-unified log formats. The high-frequency update rhythm requires plugins to support incremental synchronization and real-time event fetching, avoiding performance consumption from full fetching. The flexibility of document formats requires a pre-configured format conversion plugin to convert raw logs into standardized fields usable for review. The fluctuating false positive sample characteristics require dynamic adjustment of tool calling concurrency thresholds to prevent resource exhaustion. The rule change approval process requires tool calling to associate with change ticket approval status, ensuring review actions are synchronized with the change workflow.

How to Configure Settings

The following configurations are based on FastGPT v4.17.0.

Configuration ItemRecommended ValueRationale
toolChoiceautoAdapts to multi-tool calling scenarios for security product rule operations, automatically selecting log parsing or rule verification tools to complete review assistance
functionCallenabledSupports converting rule adjustment suggestions output by the model into executable configuration parameters, adapting to the automated output requirements of change reviews
Security Product API Timeout Threshold300–600 secondsAdapts to the delay characteristics of security product log fetching, avoiding process interruptions due to timeout during full synchronization or incremental fetching
Incremental Synchronization IntervalCalibrated through actual testing, recommended 10–30 minutesBalances data real-time performance and server resource consumption, adapting to daily or event-triggered update rhythms
Single Log Fetch LimitTop 500 entriesControls the load of a single tool call, preventing service freezes caused by excessively large single batch data
Single Log Format Conversion Limit800–1200 charactersControls the load of a single conversion, avoiding tool call failures caused by excessively large single batch data

Three Common Configuration Mistakes

  • Symptom: After calling the FastGPT API to initiate a conversation, the model generation process cannot be actively interrupted, and subsequent requests must wait for prior tasks to complete. Cause: toolChoice is not configured for interruptible mode, or the session-level task termination interface is not enabled, resulting in the request queue not being released in a timely manner.
  • Symptom: After configuring a custom URL document parsing tool, no data is returned and no error is triggered. Cause: The custom URL is not added to the data source whitelist for security product rule operations, or the content format returned by the URL exceeds the parsing range preset by the plugin.
  • Symptom: After the workflow runs, no document format results that meet the requirements are generated. Cause: The output format constraint for functionCall is not enabled, and the rule adjustment content output by the model is not converted into a standardized document field structure.

How to Confirm Configurations Are Correctly Set

  • Initiate a test rule change review request, verify that the rule adjustment suggestions output by the model can be automatically converted into executable configuration parameters, confirming that the functionCall function is working properly.
  • Configure a custom URL data source, initiate a document parsing call, check whether the returned log fields include core information such as rule ID and interception threshold, confirming that the format conversion plugin is working correctly.
  • Initiate an incremental synchronization test, check whether intercept logs from security products are fetched at the preset interval, confirming that the API timeout threshold and incremental synchronization interval configurations meet business requirements.
  • Check the cross-domain configuration of the FastGPT server, verify that external domain names can normally initiate API requests, confirming that the cross-domain settings meet the access requirements of security product rule operations.

The values provided here are common starting points and should be measured against the reader's own samples.

Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.