> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/checks/component/comp_0013.md).

# App uses AI components

<table><thead><tr><th width="138">Check ID</th><th>COMP_0013</th></tr></thead><tbody><tr><td>Category</td><td>Security</td></tr><tr><td>Summary</td><td>The Mendix platform has introduced a range of AI capabilities, including the Agent Editor, Agent Commons, and supporting connector modules. While these components enable powerful new functionality, their use introduces considerations around data privacy, model governance, and regulatory compliance — including the EU AI Act. Depending on the needs of your organization, you may wish to ensure that AI components are only used in apps where their use has been explicitly approved. This check detects the presence of known AI components in your app and flags apps where AI components are in use.</td></tr><tr><td>Options</td><td>None.</td></tr><tr><td>Pass</td><td>No known AI components are detected in your app.</td></tr><tr><td>Fail</td><td>One or more AI components are detected in your app.</td></tr></tbody></table>


---

# 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.bluestorm.io/checks/component/comp_0013.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.
