> 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-tamper-alarm-rule.md).

# LCT - Tamper Alarm Rule

The Tamper Alarm Rule for LCT devices triggers an alert when the device is either mounted or unmounted, depending on the user-defined configuration. This ensures real-time notifications for changes in the device's physical state, enhancing monitoring and security.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuDEIUAO31Hxuyg3jZleS1hRzRkdjibcm1Nc0ROu7HLWyRSxwYqsrUWoEZUwAyh4maaNBUJc5PHJt4V4fElpRYRQQpon-pRajPkXUFQ4vhpyPNLBg0fJfRpLXhqTiRxVHacI8-Aw?key=Kl1KyU1gDzenB_F0xjN17rry" alt=""><figcaption><p>LCT Tamper Alarm Rule</p></figcaption></figure>

## Steps to Set Up Tamper Alarm Rule for LCT:

1. **Access the Rule Page:**
   * Navigate to the device list, locate the desired LCT device, and open its dashboard.
   * Go to the Rules section, click on the **+** icon, and select the **Tamper Alarm Rule**.
2. **Activate the Rule:**
   * Toggle the switch at the top to enable the Tamper Alarm Rule.
3. **Name the Rule:**
   * Enter a meaningful name to identify the rule.
4. **Set the Alarm Level:**
   * From the dropdown menu, select the alarm level:
     * Critical
     * Major
     * Minor
     * Warning
   * This ensures the proper organization of all triggered alarms.
5. **Set Alarm Trigger:**
   * Define whether the alarm will be triggered when the device is **Mounted** or **Unmounted**.
6. **Configure Notification:**
   * Choose whether to send a notification:
     * **Email:** Insert up to 5 recipient email addresses for the alarm notification.
     * **None:** Select this option if no notification is required, and the alarm will only be visible on the platform.
7. **Click Save:**
   * Save the configuration to apply the Tamper Alarm 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.