> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.endorlabs.com/feedback

```json
{
  "path": "/releasenotes/previous-releases/june-2025/index",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# June 2025

We are excited to introduce the latest features and enhancements in Endor Labs.

### Endor Labs MCP server for IDE

<Badge color="purple" shape="pill">Alpha</Badge> <Badge icon="star" color="green" shape="pill">New</Badge>

Endor Labs MCP server is now available in alpha for Cursor and Visual Studio Code.

The Endor Labs MCP server integrates directly into your IDE to scan code in real-time, and catch security issues before they reach production. This workflow secures both human and AI-generated code from the moment it's written. For more information, see [Endor Labs MCP Server](/setup-deployment/mcp).

### Grant support access to your tenant

<Badge icon="star" color="green" shape="pill">New</Badge>

You can now grant the Endor Labs support team read-only access to your tenant for a limited time. This feature enables our support team to assist you more efficiently while ensuring your data remains secure and private.

For more information, see [Grant support access](/platform-administration/rbac/authorization-policies#grant-support-access).

### Finding policies for AI models

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

You can now configure two new finding policies and manage the use of AI models more effectively in your organization.

* **Restricted AI models**: Raise a finding when a repository uses an AI model that your organization has marked as restricted or allowed only in specific contexts.

* **Restricted AI model providers**: Raise a finding when a repository uses an AI model from a provider that is restricted based on your organization’s policy.

For more information, see [Detect AI models](/secure-ai-coding/ai-model-discovery#detect-ai-models).

### Manually upgrade finding policies

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

You can now upgrade a finding policy when a new version is available. Policy upgrades may include changes such as updated Rego code, new fields, parameters, or tags. After upgrading, you cannot revert the policy to its previous version.

For more information, see [Upgrade a finding policy](/platform-administration/policies/finding-policies#upgrade-a-finding-policy).

### Resolving package names from prop files

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

endorctl now evaluates MSBuild properties from files like `Directory.Build.props`, enabling resolution of package names and versions defined using variables.

For more information, see [Resolving package names from props files](/scan/sca/dotnet#resolving-package-names-from-props-files).

### Group findings by dependency

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

Findings in the **SCA**, **Vulnerability**, and **Container** categories are now grouped by **Dependency** by default, making it easier to review your scans.

For more information, see [View findings](/inventory-insights/findings).

### AI model discovery in Endor Labs monitoring scans

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

Endor Labs now automatically detects AI models during SCA scans when using the GitHub App, Bitbucket App, Azure DevOps App, and GitLab App. You can view AI models from the **AI Inventory**.

For more information, see [View AI model findings using Endor Labs GitHub App](/secure-ai-coding/ai-model-discovery#view-ai-model-findings-through-monitoring-scans).

### Components field support for Jira tickets

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

You can now configure the Jira integration in Endor Labs to automatically populate the **Components** field in Jira tickets for both company-managed and team-managed Jira projects.

For more information, see [Integrate Jira with Endor Labs](/integrations/jira#configure-jira-integration-on-endor-labs).

### Exclude all child namespaces

<Badge icon="check" color="blue" shape="pill">Enhancement</Badge>

By default, the Endor Labs dashboard includes data from all child namespaces. Use the **All child namespaces excluded** toggle to exclude child namespaces and view data and metrics for only the selected namespace.

For more information, see [Namespaces in Endor Labs](/platform-administration/namespaces#namespaces-in-an-organization).