> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/administration/admin-console/resources/dev-machine-guard.md).

# Dev Machine Guard

The Dev Machine Guard tab in the Resources section shows whether Dev Machine Guard is enabled for your organization and the default scan frequency that applies to enrolled devices. Use this tab to confirm the org-level configuration, then jump to the full Dev Machine Guard dashboard to review devices and manage device policies.

####

{% hint style="info" %}
For the full Dev Machine Guard product documentation, including device enrollment, IDE extension and AI agent policies, MCP server monitoring, and OSS dependency tracking, see the [Dev Machine Guard section](https://docs.stepsecurity.io/dev-machine-guard/).
{% endhint %}

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FgetJaIKiGHJ0lWLqx34Y%2FScreenshot%202026-05-08%20at%2012.17.55.png?alt=media&amp;token=c3c4d487-67fc-4ae4-a0f9-924adeb357a0" alt=""><figcaption></figcaption></figure>

### What you can do here

* **Confirm Dev Machine Guard is enabled:** The Configuration Details panel shows whether the agent is enabled for your organization.
* **Review the default scan frequency:** This is how often the Dev Machine Guard agent scans an enrolled device by default. The default is 4 hours.
* **Open the Dev Machine Guard dashboard:** Click **Visit Dashboard** in the top right to open the full Dev Machine Guard dashboard, where you can review enrolled devices, IDE extension and AI agent inventories, MCP servers, agent skills, installed packages, and suspicious files, and manage device policies.


---

# 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.stepsecurity.io/administration/admin-console/resources/dev-machine-guard.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.