> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-increase-severity-rule.md).

# LCT - Increase Severity Rule

The **Increase Security Rule** is designed to **continuously monitor active alarms** and escalate their severity level over time if they remain unresolved. At each defined **time interval**, the rule checks whether the alarm is still in an **ON (active) state**. If the alarm persists, the system automatically increases its severity level step by step until it reaches the highest level of **Critical**. This rule enhances security by ensuring that prolonged or unattended alarms receive heightened attention, prompting quicker action to mitigate potential risks.

<figure><img src="/files/aHYXqXpzitKvHWYtnIlr" alt=""><figcaption><p>Increase Severity</p></figcaption></figure>

## Steps to Set Up the Increase Severity Rule for LCT:

1. **Go to Device:**\
   Navigate to the **device list**, locate the desired LCT device, and open its **dashboard**.
2. **Access Rules Section:**\
   Open the **Rules** section of the device dashboard, click on the **+ icon**, and select the **Increase Severity**.
3. **Activate Rule:**\
   Toggle the switch to activate the rule.
4. **Insert Rule Name:**\
   Enter a meaningful name for the rule.
5. **Insert Alarm Type**\
   Use the + icon to add more than one type, up to five types max.
6. **Specify the interval:**\
   Insert the numerical value of the interval.
7. **Define Interval Type:**\
   Select if the interval will be in Minutes or Hours
8. **Save Configuration:**\
   Click **Save** to apply and activate the rule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-increase-severity-rule.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.