导航|地址|刷新
Actions

Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/ruleset-engine/llms.txt
Use this file to discover all available pages before exploring further.

Docs Directory API SDKs Changelog

Search

Log in

Ruleset Engine

/

Overview

About

Overview

Phases

Rulesets

Rules

Basic API operations

View rulesets

Add rules to phase entry point rulesets

Deploy rulesets

Work with managed rulesets

Overview

Deploy a managed ruleset

Override a managed ruleset

Override examples

Overview

Set WordPress rules to Block

Enable only Joomla rules

Enable only selected rules

Deploy a managed ruleset with ruleset, tag, and rule overrides

Adjust the sensitivity of an HTTP DDoS rule to Low

Adjust an L3/4 DDoS rule ↗

Create an exception

Work with custom rulesets

Overview

Create a custom ruleset

Add rules to a custom ruleset

Deploy a custom ruleset

Rules language

Overview

Expressions

Overview

Edit in the dashboard

Operators and grouping symbols

Values

Actions

Fields

Overview

Fields reference

Functions

Rulesets API

Overview

JSON objects

Endpoints

List and view rulesets

Create a ruleset

Update or deploy a ruleset

Add a rule to a ruleset

Update a rule in a ruleset

Delete a rule in a ruleset

Delete a ruleset

Reference

Phases list

Agent resources

Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Ruleset Engine llms.txt ↗

Ruleset Engine llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗

Home

/Ruleset Engine

/Rules language

/Actions

Actions

Last updated Apr 23, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewSupported actions

The action of a rule tells Cloudflare how to handle matches for the rule expression.

Supported actions

The table below lists the actions available in the Rules language.

Some actions like Block, called terminating actions, will stop the evaluation of the remaining rules. The Skip action will skip the evaluation of some rules when there is a match, but the exact behavior will depend on the rule configuration.

The available actions depend on the phase where you are configuring the rule. Refer to each product’s documentation for details on the phase(s) supported by that product.

Action Description Terminating action?
Non-Interactive Challenge

API value:
js_challenge

Useful for ensuring that bots and spam cannot access the requested resource; browsers, however, are free to satisfy the challenge automatically.

The client that made the request must pass a non-interactive Cloudflare challenge before proceeding.

If successful, Cloudflare accepts the matched request; otherwise, it is blocked.
Yes
Managed Challenge

API value:
managed_challenge

Helps reduce the lifetimes of human time spent solving CAPTCHAs across the Internet.

Depending on the characteristics of a request, Cloudflare will dynamically choose the appropriate type of challenge from the following actions based on specific criteria:

Show a non-interactive challenge page.

Show a custom interactive challenge (such as click a button).
Yes
Interactive Challenge

API value:
challenge

Useful for ensuring that the visitor accessing the site is human, not automated.

The client that made the request must pass an interactive challenge.

If successful, Cloudflare accepts the matched request; otherwise, it is blocked.
Yes
Block

API value:
block

Matching requests are denied access to the site.

Depending on the Cloudflare product performing the block action, the HTTP status code can be 403 (most security features) or 429 (for example, rate limiting rules).

Customers on paid plans can customize the HTML error page displayed to website visitors due to the block action. Refer to Error Pages for more information.

Customers in Pro plans and above can customize the response (HTML, JSON, XML, or plain text) and the response status code for each custom rule or rate limiting rule that triggers a block action.
Yes
Skip

API value:
skip

Allows user to dynamically skip one or more security features or products for a request.

Depending on the rule configuration, matching requests will skip the evaluation of one or more security features or products:

Skip all remaining rules in the current ruleset

Skip all remaining rules in the current phase (zone-level only option)

Skip rulesets

Skip rules of a ruleset

Skip phases

Skip specific security products that are not based on the Ruleset Engine

The available skip options depend on the phase where you configure the rule. Refer to each product’s documentation for details.

If you configure a rule with the Skip action at the account level it will only affect rules/phases configured at the account level, not at the zone level. To skip rules/phases at the zone level you must configure a rule with the Skip action at the zone level.

No

(but some rules may be skipped)
Log

API value:
log

Records matching requests in the Cloudflare Logs.

Only available on Enterprise plans.

Recommended for validating rules before committing to a more severe action.
No
Execute

API value:
execute

Executes the rules in the ruleset specified in the rule configuration. You can specify a managed ruleset or a custom ruleset to execute.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns.
No
Rewrite

API value:
rewrite

Rewrites the request (or response) by adjusting the URI path, query string, and/or HTTP request/response headers, according to the rule configuration.

Only available in:

Transform Rules, in phases http_request_transform, http_request_late_transform, and http_response_headers_transform. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a Transform Rule.

WAF custom rules checking for exposed credentials, in the http_request_firewall_custom phase at the account level. In the Cloudflare dashboard, this action is called Exposed-Credential-Check Header.
No
Redirect

API value:
redirect

Navigates the user from a source URL to a target URL, according to the rule configuration, by replying with an HTTP redirect.

Only available for Single Redirects and Bulk Redirects.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a redirect rule or a bulk redirect rule.

Yes
Route

API value:
route

Adjusts the Host header, Server Name Indication (SNI), resolved hostname, and/or resolved destination port of incoming requests.

Only available for Origin Rules, in the http_request_origin phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create an origin rule.

No
Set Configuration

API value:
set_config

Changes the configuration settings of one or more Cloudflare products.

Only available for Configuration Rules, in the http_config_settings phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a Configuration Rule.

No
Compress Response

API value:
compress_response

Defines compression settings for delivering responses to website visitors.

Only available for Compression Rules, in the http_response_compression phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a compression rule.

No
Set Cache Settings

API value:
set_cache_settings

Cache Rules allows you to customize cache settings on Cloudflare.

Only available for Cache Rules, in the http_request_cache_settings phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a cache rule.

No
Serve Error

API value:
serve_error

Serves error content to the website visitor, according to the custom error rule configuration.

Only available for Custom Error Rules, in the http_custom_errors phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a custom error rule.

Yes
Log custom field

API value:
log_custom_field

Configures custom fields for Logpush jobs in a zone.

Only available for custom fields, in the http_log_custom_fields phase.

In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, configure custom log fields for Logpush jobs.

Yes

Note

Cloudflare Firewall Rules, now deprecated, supports a different set of actions, including the Allow and Bypass actions. Refer to Firewall rules actions for more information.

PreviousValuesNextOverview

Was this helpful?

YesNo

Edit pageReport issue

On this page

Overview

Supported actions

Edit pageReport issue

Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search

Company
AboutCareersInvestorsPressPress kitGlobal network

Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG

Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse

Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog

Developers
DocumentationLearning centerCommunity

Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform

Start BuildingLog In

© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices

Docs

------
导航页打开网址

Action	Description	Terminating action?
Non-Interactive Challenge API value: js_challenge	Useful for ensuring that bots and spam cannot access the requested resource; browsers, however, are free to satisfy the challenge automatically. The client that made the request must pass a non-interactive Cloudflare challenge before proceeding. If successful, Cloudflare accepts the matched request; otherwise, it is blocked.	Yes
Managed Challenge API value: managed_challenge	Helps reduce the lifetimes of human time spent solving CAPTCHAs across the Internet. Depending on the characteristics of a request, Cloudflare will dynamically choose the appropriate type of challenge from the following actions based on specific criteria: Show a non-interactive challenge page. Show a custom interactive challenge (such as click a button).	Yes
Interactive Challenge API value: challenge	Useful for ensuring that the visitor accessing the site is human, not automated. The client that made the request must pass an interactive challenge. If successful, Cloudflare accepts the matched request; otherwise, it is blocked.	Yes
Block API value: block	Matching requests are denied access to the site. Depending on the Cloudflare product performing the block action, the HTTP status code can be 403 (most security features) or 429 (for example, rate limiting rules). Customers on paid plans can customize the HTML error page displayed to website visitors due to the block action. Refer to Error Pages for more information. Customers in Pro plans and above can customize the response (HTML, JSON, XML, or plain text) and the response status code for each custom rule or rate limiting rule that triggers a block action.	Yes
Skip API value: skip	Allows user to dynamically skip one or more security features or products for a request. Depending on the rule configuration, matching requests will skip the evaluation of one or more security features or products: Skip all remaining rules in the current ruleset Skip all remaining rules in the current phase (zone-level only option) Skip rulesets Skip rules of a ruleset Skip phases Skip specific security products that are not based on the Ruleset Engine The available skip options depend on the phase where you configure the rule. Refer to each product’s documentation for details. If you configure a rule with the Skip action at the account level it will only affect rules/phases configured at the account level, not at the zone level. To skip rules/phases at the zone level you must configure a rule with the Skip action at the zone level.	No (but some rules may be skipped)
Log API value: log	Records matching requests in the Cloudflare Logs. Only available on Enterprise plans. Recommended for validating rules before committing to a more severe action.	No
Execute API value: execute	Executes the rules in the ruleset specified in the rule configuration. You can specify a managed ruleset or a custom ruleset to execute. In the Cloudflare dashboard, this action is not listed in action selection dropdowns.	No
Rewrite API value: rewrite	Rewrites the request (or response) by adjusting the URI path, query string, and/or HTTP request/response headers, according to the rule configuration. Only available in: Transform Rules, in phases http_request_transform, http_request_late_transform, and http_response_headers_transform. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a Transform Rule. WAF custom rules checking for exposed credentials, in the http_request_firewall_custom phase at the account level. In the Cloudflare dashboard, this action is called Exposed-Credential-Check Header.	No
Redirect API value: redirect	Navigates the user from a source URL to a target URL, according to the rule configuration, by replying with an HTTP redirect. Only available for Single Redirects and Bulk Redirects. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a redirect rule or a bulk redirect rule.	Yes
Route API value: route	Adjusts the Host header, Server Name Indication (SNI), resolved hostname, and/or resolved destination port of incoming requests. Only available for Origin Rules, in the http_request_origin phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create an origin rule.	No
Set Configuration API value: set_config	Changes the configuration settings of one or more Cloudflare products. Only available for Configuration Rules, in the http_config_settings phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a Configuration Rule.	No
Compress Response API value: compress_response	Defines compression settings for delivering responses to website visitors. Only available for Compression Rules, in the http_response_compression phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a compression rule.	No
Set Cache Settings API value: set_cache_settings	Cache Rules allows you to customize cache settings on Cloudflare. Only available for Cache Rules, in the http_request_cache_settings phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a cache rule.	No
Serve Error API value: serve_error	Serves error content to the website visitor, according to the custom error rule configuration. Only available for Custom Error Rules, in the http_custom_errors phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, create a custom error rule.	Yes
Log custom field API value: log_custom_field	Configures custom fields for Logpush jobs in a zone. Only available for custom fields, in the http_log_custom_fields phase. In the Cloudflare dashboard, this action is not listed in action selection dropdowns. To use this action, configure custom log fields for Logpush jobs.	Yes