---
schema_version: "1"
id: 20a4cde55e70e5ed764be1b2e89ee9375af807d08d17d0db95fad637a5763ba4
title: Viewing Service Details in the Portfolio
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/general/exp-services-view-details.md
canonical_url: https://docs.mulesoft.com/general/exp-services-view-details
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 90faccd8a42869feff8e307cd0fc389d38b0ce5ccb5e1ac0e2a5530f9e329716
description: MuleSoft Documentation Site
latest: true
---
---
product: Getting Started
keywords: view service details, service detail page, anypoint exchange, exchange services, service tabs, mulesoft exchange
---

# Viewing Service Details in the Portfolio

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

View scanner read policies, deployments, monitoring, and conformance for a service from one detail
page in **Portfolio**. Open any service, including an API, agent, MCP server, Model Proxy, or
gateway, to review current status, cost, and relationships. Use this page to validate applied
controls and track changes without switching contexts.

> [!NOTE] Automate service lookups using the MuleSoft MCP Platform Server. For details, see
> [fetch\_services](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools-platform#fetch-services) and related
> Search and Discovery tools in the MuleSoft MCP Platform Server Tool Reference.

## Before You Begin

Before getting started, make sure you have:

- An Anypoint Platform account.

- One of these permissions:

  - Exchange: Exchange Viewer

  - Exchange: Exchange Contributor

  - Exchange: Exchange Administrator

  For more information, see [Enhanced Experience Permissions](https://docs.mulesoft.com/general/exp-home-start#permissions).

## Service Detail Tabs

The page is organized into tabs. The table lists tabs, what they show, and whether they appear on
the detail page for each catalog type:

- **Yes** means the tab appears in typical configurations.

- **No** means the tab is omitted or you use another area of the experience for the same job (see
  the note after the table).

Labels and fields inside a tab can differ by service type and release. For end-to-end portfolio
tasks that reference these tabs, see [Enhanced MuleSoft Experience Overview](https://docs.mulesoft.com/general/exp-overview). tab can
differ by service type and release. For end-to-end portfolio tasks that reference these tabs, see
[Enhanced MuleSoft Experience Overview](https://docs.mulesoft.com/general/exp-overview).

<table><colgroup><col> <col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Tab</th><th>What You See</th><th>API</th><th>Agent</th><th>MCP Server</th><th>Model Proxy</th><th>Gateway</th></tr></thead><tbody><tr><td><p><strong>Overview</strong></p></td><td><p>Short summary of what the service does and its specification.</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td></tr><tr><td><p><strong>Instances</strong></p></td><td><p>Deployed instances, environments (for example production or sandbox), and gateways when that catalog type supports instances. When Akamai API Security is enabled and scan data is available for this service, the table also shows a <strong>Security Risk</strong> column with a color-coded risk level per instance (Low, Medium, High, or Critical). Risk levels are per-instance — the same API can show different risk levels across environments.</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Each Model Proxy is exactly one instance so there is no <strong>Instances</strong> tab.</p></td><td><p>No</p></td></tr><tr><td><p><strong>Policies</strong></p></td><td><p>Governance policies attached to the service or its instances (access, data, performance, compliance, and related domains your organization uses). For APIs discovered by scanners, this tab shows read policies from Amazon API Gateway, Google Apigee, Azure API Management, and Kong Gateway. If the instance uses a Kong gateway, the listed policies are gateway-level policies (plugins). Other service-level policies (plugins) can also apply. On supported gateways, you can also manage native policies from this tab. See <a href="https://docs.mulesoft.com/general/exp-policies-apply-manage">Applying and Managing Policies</a>.</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>No</p></td></tr><tr><td><p><strong>Monitoring</strong></p></td><td><p>Runtime metrics and analytics for health and usage when the system surfaces them for the service or gateway you are viewing.</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>No</p></td></tr><tr><td><p><strong>Conformance</strong></p></td><td><p>Compliance score and rule-level analysis for conformance reporting where that tab is available. When Akamai API Security is enabled, the tab includes an <strong>Akamai</strong> section with a risk score overview, a findings table (endpoint-level vulnerabilities with severity, OWASP API Top-10 tags, and compliance framework tags), and an incidents table (aggregated security incidents). Select a finding to view details and see recommended remediation policies you can apply directly from this page.</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>Yes</p></td><td><p>No</p></td><td><p>No</p></td></tr></tbody></table>

> [!NOTE]
>
> - **Instances** tab is available on **Agents**, **MCP Servers**, and **APIs**; **Model Proxies**
>   and **Gateways** do not include an **Instances** tab. See
>   [Enhanced MuleSoft Experience Overview](https://docs.mulesoft.com/general/exp-overview).
>
> - **Conformance** on the detail page aligns with **Agents**, **APIs**, and **MCP Servers**; for
>   gateways, compliance work is framed through **Governance** and related flows at the scope the
>   system supports. See [Enhanced MuleSoft Experience Overview](https://docs.mulesoft.com/general/exp-overview).

## Open a Service Detail Page

1.  In **Portfolio**, open the catalog for the service type (for example **APIs** or **Agents**).

2.  Use the search box to find the service by name or description, or scan the list or grid.

3.  Select the service card to open its detail page.

## View Read Policies Discovered by Scanners

If a provider scanner has policy-read scopes configured, the **Policies** tab shows discovered
policy entries for that API instance. The tab lists policy names and mapped governance context, such
as category and apply level, when the provider returns that metadata. For providers that expose
policy status, the tab also shows whether a policy is enabled so teams can validate scanner coverage
and conformance inputs from the latest scan snapshot.

1.  In **Portfolio**, open **APIs** and select an API discovered by a provider scanner.

2.  Open the **Policies** tab on the service detail page.

3.  Review read policies imported from Amazon API Gateway, Google Apigee, Azure API Management, or
    Kong Gateway.

4.  Use the policy list to confirm applied controls before governance reviews or conformance
    analysis.

Policy visibility depends on the last successful scanner run, not on a live provider query. If
required provider scopes or roles are missing, policy results can be incomplete or unavailable.
Policy fields such as status, apply level, and detail can vary by provider. If expected policies are
missing, check scanner run status and history in **Providers**.

Reading policies is view-only. To create, edit, enable, disable, or remove policies on Anypoint and
external gateway providers from this tab, see
[Applying and Managing Policies](https://docs.mulesoft.com/general/exp-policies-apply-manage) and
[Managing Policies on Gateway Providers](https://docs.mulesoft.com/general/exp-policies-overview).

## Manage Native Policies

On supported gateways, the **Policies** tab also lets you manage the native policies applied to an
instance. Depending on the gateway and your permissions, you can edit, remove, or enable and disable
a policy directly from this tab. Policies that are outside your instance’s scope appear in a
read-only (view-only) state, without edit, remove, or enable/disable actions.

Policy write actions are tracked. To confirm whether an apply, edit, enable, disable, or remove
completed on the gateway, review the **Activity log** tab of the instance detail page. See
[Tracking Policy Operations in the Activity Log](https://docs.mulesoft.com/general/exp-policies-activity-log).

For the full apply and management workflow, see
[Applying and Managing Policies](https://docs.mulesoft.com/general/exp-policies-apply-manage).

## See Also

- [Enhanced MuleSoft Experience Overview](https://docs.mulesoft.com/general/exp-overview)

- [Adding Services to Your Portfolio](https://docs.mulesoft.com/general/exp-services-add-to-portfolio)

- [Create a Scanner for Provider Services](https://docs.mulesoft.com/general/exp-services-connect-providers-to-add)

- [Register Services Manually](https://docs.mulesoft.com/general/exp-services-register-manually)

- [Create MCP Servers with MCP Bridge](https://docs.mulesoft.com/general/exp-services-create-mcp-server)

- [Configuring Semantic Routing Services](https://docs.mulesoft.com/general/model-proxy-semantic-service)

- [Creating and Managing Instances of Services](https://docs.mulesoft.com/general/exp-instances-add)

- [Monitoring Services in Your Portfolio](https://docs.mulesoft.com/general/exp-services-monitoring)

- [View Detailed Metrics for Your Services](https://docs.mulesoft.com/general/exp-services-view-detailed-metrics)