> ## Documentation Index
> Fetch the complete documentation index at: https://ngrok.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Deny Action
> The Deny action enables you to reject incoming requests on your endpoints before they make it to your upstream service.
export const ConfigField = ({title, type, cel = false, defaultValue = false, required = false, children}) => {
const id = `config-${title.replace(/\.|\s|\*/g, "_")}`;
return
{title}
{type &&
{type}
}
{defaultValue &&
default:
{defaultValue}
}
{required &&
Required
}
{cel &&
Supports CEL
}
{children}
;
};
The **Deny** Traffic Policy action enables you to reject incoming requests on
your endpoints before they make it to your upstream service.
## Configuration reference
The [Traffic Policy](/traffic-policy/) configuration
reference for this action.
### Supported phases
`on_tcp_connect`, `on_http_request`
### Type
`deny`
### Configuration fields
This action does not have any configuration fields for TLS / TCP endpoints.
The response status code to return back to the client when the request is denied.
## Behavior
When this action is executed, the upstream server is never reached and a
response is immediately returned and no further actions or rules in the policy
configuration will be executed.
When this action is executed, the upstream server is never reached and a
response is immediately returned and no further actions or rules in the policy
configuration will be executed.
### Custom content
The deny Traffic Policy action will not send back a response body to the client.
To send back a response body, use the [`custom-response`](/traffic-policy/actions/custom-response)
action.
### Terminating action
This is a **terminating action**. It will return a response and cause Traffic Policy processing to end without executing any further Actions.
## Examples
### Deny all traffic
The following [Traffic Policy](/traffic-policy/)
configuration will deny all inbound traffic on your endpoint.
#### Example Traffic Policy document
```yaml policy.yml theme={null}
on_tcp_connect:
- actions:
- type: deny
```
```json policy.json theme={null}
{
"on_tcp_connect": [
{
"actions": [
{
"type": "deny"
}
]
}
]
}
```
#### Example request
```bash theme={null}
$ telnet 5.tcp.ngrok.io 22984
Trying...
Connected to 5.tcp.ngrok.io.
Connection closed by foreign host.
```
In this example, a connection attempt to `5.tcp.ngrok.io:22984` using the
`telnet` command and ngrok immediately closes the connection.
### Deny traffic with a 404 status code
The following [Traffic Policy](/traffic-policy/)
configuration will deny all inbound traffic with a `404` on your endpoint.
#### Example Traffic Policy document
```yaml policy.yml {3-10} theme={null}
on_http_request:
- actions:
- type: deny
config:
status_code: 404
```
```json policy.json {5-10} theme={null}
{
"on_http_request": [
{
"actions": [
{
"type": "deny",
"config": {
"status_code": 404
}
}
]
}
]
}
```
#### Example request
```curl theme={null}
$ curl https://example.ngrok.app
```
```http theme={null}
HTTP/2 404 Not Found
```
In this example, a connection attempt to `example.ngrok.app` using the
`curl` command and ngrok immediately closes the connection with a `404` status
code.
## Action result variables
The following variables are made available for use in subsequent expressions and
CEL interpolations after the action has run. Variable values will only apply
to the last action execution, results are not concatenated.
This action does not set any variables after it has been executed.