Getting started Community Training Tutorials Documentation APIs, AI & Tools
Agent detail pages no longer show Unknown in the Updated field.
The enhanced MuleSoft experience is a unified workspace for managing, governing, and monitoring AI-connected integration assets, including agents, APIs, Model Context Protocol (MCP) servers, model proxies, and gateways. Teams use it to register services, apply governance strategies, monitor runtime health, and optimize costs from one portfolio view instead of working across disconnected tools.
You can now monitor traffic through Omni Gateway by applying the Akamai API Security (Omni Gateway) policy to your API instances. This traffic includes:
Internal traffic between services (east-west traffic).
External traffic to endpoints you can’t register at the Akamai edge, such as MuleSoft-managed CloudHub endpoints.
For more information, see Monitor Traffic Through Omni Gateway.
When you apply an Amazon API Gateway policy from agentic tools through the Platform MCP server, you can now scope it to a path, an HTTP method, or an operation, which combines a path and a method. The agent shows the scopes that the policy supports and asks which scope and target you want. The policy details it returns now include the scope each policy applies to.
The Review step of the governance strategy Create Policy wizard now tells you when a policy supports more granular scopes, which you can select in the instance-level policy experience.
MuleSoft Agent now returns catalog and governance assets from child business groups for users in the root business group.
MuleSoft Agent in Slack and Microsoft Teams now takes fewer steps to answer, so responses arrive faster. In Microsoft Teams, answers now appear as they’re generated instead of all at once.
MuleSoft Agent in Slack and Microsoft Teams now supports GraphQL and the additional tools available in the embedded MuleSoft Agent.
Third-party libraries are upgraded to address reported security vulnerabilities.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
Agent detail pages no longer show Unknown in the Updated field. |
W-23016618 |
The advanced options for policies that you apply to agents and MCP servers no longer include the option to apply the policy conditionally by HTTP method. |
W-23267358 |
MuleSoft Agent now returns catalog and governance assets from child business groups for users in the root business group. |
W-23926623 |
The See Benchmark view on the Optimizations tab now shows an indicator for additional models. |
W-23953679 |
Users who don’t have access to Cost Management now see a permission message instead of a "No LLM proxies found for the selected filters" message. |
W-23983310 |
Optimization cards now show the See Benchmark link and the Why this policy section, and show potential savings in dollars per month instead of tokens. |
W-23998776 |
Searching model proxies on the Optimizations tab now matches instance IDs in addition to names. |
W-24010016 |
The submit button on policy forms in the Platform MCP server now reads Apply policy instead of Request policy creation. |
W-24027218 |
MuleSoft Agent in Slack and Microsoft Teams now tells you when it can’t find data instead of showing an empty card. |
W-24105572 |
A2A policies now appear in the policy catalog for A2A v1.0 agent instances, so you can apply policies such as A2A Token Based Rate Limit. |
W-24119017 |
The MuleSoft Agent welcome message in Microsoft Teams no longer appears twice when you add the agent to a channel or direct message. |
W-24135116 |
The error message that appears when a user who isn’t an Anypoint Platform administrator grants access permissions is now clearer. |
W-24159946 |
Assets discovered by scanners no longer appear as managed instances with options to apply policies or as deployed to the Production environment. |
W-24276575 |
The Security tab now shows data from all environments instead of only the default environment. |
W-24366135 |
Third-party libraries are updated to resolve reported security vulnerabilities. |
W-24505378 |
You can now create a ServiceNow AI agent scanner to discover agents from ServiceNow.
You can now create a Kong Gateway scanner to discover MCP servers from Kong Gateway.
You can now use OAuth 2.0 Authorization Code for Google Vertex AI scanners to create, authorize, and test the provider connection before you continue scanner setup.
For more information, see Scanner OAuth Authorization.
You can now apply open policies at the path, operation, or HTTP method level for providers that require a finer scope than the API instance, such as Amazon API Gateway. When an open policy maps to more than one native policy, the Review step tells you, and the policy list shows the path or operation that each policy applies to.
The Platform MCP server now includes tools to apply open policies and to apply and edit native policies from agentic tools, such as Claude and Cursor. A new skill guides agents through applying an open policy.
You can now register remote MCP servers that require browser-based OAuth 2.1 Authorization Code with PKCE authentication.
You can now publish a custom LLM provider to Anypoint Exchange as an llm-metadata.json classifier asset and select it as the provider for a model proxy route.
For more information, see Publishing Custom LLM Providers to Anypoint Exchange.
Policy configuration forms now support conditional fields and mutually exclusive configuration options, such as the signing key length in JWT Validation and the JWKS source in Apigee Verify JWT.
The Configure Policy step of the governance strategy Create Policy wizard now shows the providers that support the selected open policy.
Policy validation errors now appear in Spanish when the UI language is Spanish.
Dropdowns now support type-ahead search, so you can quickly find items in long lists, such as AWS regions.
The Session Token field is now available for Amazon Bedrock routes in dynamic mode, so callers that use short-lived AWS credentials can route requests through a model proxy.
MuleSoft Agent in Microsoft Teams now shows the same loading, authentication, and error messages as in Slack, and suggests follow-up actions after each answer.
MuleSoft Agent now responds faster in Slack and Microsoft Teams.
The MuleSoft bot is now added to a Microsoft Teams channel automatically when you select the channel, and the bot name now includes the region, such as MuleSoft (EU).
Instance detail, gateway, and policy template pages load faster.
Universal policies are renamed to open policies, and the Omni & MuleSoft badge for advanced policies is renamed to Omni & Mule Gateway.
The Policies tab and activity log no longer appear for MCP server and agent instances that are managed by third-party gateways, such as Azure API Management or Amazon API Gateway, because applying policies isn’t supported for these providers. Previously, the tab showed an Apply Policy button that returned an error.
Azure OpenAI no longer appears as a provider option when you create a semantic service, because it isn’t supported.
The welcome dialog now reflects the Agent Fabric brand.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
Public MuleSoft catalog assets no longer show a Not Validated conformance badge. |
W-22108561 |
The |
W-22624722 |
The Gateways page no longer lists a self-managed gateway that doesn’t exist in Anypoint Platform. |
W-22732162 |
The |
W-22831480 |
Filters on portfolio pages now narrow results consistently. |
W-22848133 |
Governance strategies created with the |
W-22854736 |
Agent detail pages no longer show an unknown environment. |
W-23017333 |
The |
W-23059789 |
MuleSoft Agent in Slack and Microsoft Teams now sends each response as one message instead of several messages. |
W-23553477 |
Creating a Trusted MCP server through MuleSoft Agent in Slack no longer fails at gateway selection. |
W-23640564 |
Installing the Slack app now succeeds for organizations that have an orphaned Slack connection. |
W-23756773 |
Custom asset icons now appear in the portfolio catalog, not only on the asset detail page. |
W-23815011 |
Adding or removing a model proxy route no longer resets the client identifier configuration in the LLM Proxy Core policy, so token tracking continues to work. |
W-23824232, W-24138884 |
The Amount Saved card on the agent dashboard now includes only request compression savings. |
W-23943885 |
The Saved column on the MCP Servers tab of the Optimizations page now shows a trend indicator. |
W-23954561 |
The applied policy count for Payload Optimization now updates after you apply a subpolicy. |
W-23955262 |
The MCP Servers tab on the Optimizations page now paginates results when there are more than 10 MCP servers. |
W-23955499 |
API instance names on Cost Management opportunity cards now appear as links. |
W-23974322 |
Bulk update failure messages for alerts are now shorter. |
W-23980698 |
Selecting the MuleSoft logo in the navigation sidebar now opens the home page. |
W-23997715 |
MCP clients no longer need the |
W-24006913 |
You can now use the keyboard to navigate table rows. |
W-24015335 |
A provisioning failure banner no longer appears for a Trusted MCP server that provisioned successfully after a retry. |
W-24046223 |
Editing a disabled open policy on a MuleSoft API instance now shows the saved configuration instead of empty fields. |
W-24079553 |
The consumer endpoint of a model proxy is now always editable, and the port is editable on self-managed gateways and limited to 8081 or 8082 on managed gateways. |
W-24087973 |
The model proxy configuration summary now shows the environment name instead of the environment type, and shows the input format. |
W-24104747 |
Users who aren’t organization administrators can now select a model when configuring a model proxy fallback route. |
W-24117065 |
Saving a model wallet that contains an Amazon Bedrock budget no longer fails with a "model isn’t recognized" error. |
W-24119805 |
The cost and tokens toggle on the Optimizations tab now works without first using it on the Budgets tab. |
W-24149250 |
MCP Bridge now recognizes roles that are assigned through teams when checking permissions. |
W-24156034 |
The Performance page now loads available data when an optional query fails, instead of failing to load entirely. |
W-24178872 |
Users who have the documented API Manager permissions can now create a model proxy without the Organization Administrator role. |
W-24194029 |
Policy configuration fields that accept multiple values no longer split values that contain commas, such as Cedar rules in Attribute-Based Access Control. |
W-24198588 |
Creating an automated policy for A2A v1 agents no longer fails with an "Invalid endpoint types" error. |
W-24198627 |
MuleSoft Agent responses in Microsoft Teams no longer refer to Slack. |
W-24215212 |
Model names now appear when users who have the documented permissions create model wallet budgets or configure model-based routing. |
W-24247083 |
Model detail pages now list model wallets from all environments instead of only the default environment. |
W-24254296 |
Numeric policy fields with fractional steps now show rounded values, such as 0.84, instead of values such as 0.8099999999999999. |
W-24255976 |
Selecting View Optimization in the opportunities carousel now updates the page URL. |
W-24269008 |
Logging in after a session times out no longer fails with an "Invalid OAuth state" error. |
W-24276489 |
You can now edit AWS Signature Injection policies without field errors. |
W-24276857 |
Selecting a model wallet on the Budgets tab now opens the wallet in its own environment. |
W-24280601 |
The Request model override field is now optional for model-based and semantic routing. |
W-24313182 |
An IP address validation error no longer remains after you replace an invalid IP address with a valid one in policy configuration. |
W-24359644 |
Editing a policy on a model proxy route now opens the configuration for that route when more than one route has the same policy. |
W-24360920 |
Model proxies that use the Gemini format now handle streaming responses correctly. |
W-24363980 |
Model proxy descriptions are now limited to 256 characters to match Exchange, so creating a model proxy with a longer description no longer fails. |
W-24377785 |
New model proxy routes no longer show NVIDIA as the provider when you haven’t selected one. |
W-24387103 |
Model proxies with OpenAI and Mistral routes now save without a duplicated routing headers error. |
W-24387105 |
Semantic routing is no longer available for model proxies that use the Anthropic or Gemini input format, because it isn’t supported for these formats. |
W-24392230 |
Creating a model proxy with an Amazon Bedrock OpenAI route no longer fails with a 400 error. |
W-24424271 |
Selecting a self-managed Omni Gateway when editing a model proxy no longer shows an endpoint retrieval error that blocks saving. |
W-24440299 |
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
MuleSoft Agent responses are no longer truncated mid-sentence. |
W-22511562 |
Third-party libraries are updated to resolve reported security vulnerabilities. |
W-23323287 |
The Updated field on service and instance detail pages now uses the canonical Platform API timestamps instead of deployment or audit fallbacks. |
W-23817531 |
The enhanced experience now loads after you select Go to enhanced experience. |
W-23909031 |
The MuleSoft Agent now returns a response instead of failing to reply. |
W-23926482 |
The agent chat no longer renders a blank turn when the LLM gateway returns a 5xx error mid-answer. |
W-23942921 |
The MuleSoft Agent now calls the correct backend tool. |
W-23973420 |
The Optimizations column now shows the correct number of applied optimizations. |
W-24010562 |
Applying a policy through the Platform MCP server now succeeds instead of failing with a "policy apply failed (unknown)" error. |
W-24027214 |
Payload compression savings now appear in Cost Management even when JWT client ID validation is skipped, so the Amount Saved and ROI dashboards no longer report zero savings. |
W-24028032 |
The Playground now applies manually configured authentication, including API Key, Bearer, Basic, and OAuth 2.0, to outgoing requests when the API spec doesn’t declare a security scheme. |
W-24061141 |
The Agents modal chart now loads data instead of appearing empty. |
W-24091631 |
The Token Usage & Response Time chart now shows estimated usage without optimization separately from tokens used, so savings are visible. |
W-24100260 |
Cost Management entitlement gating is now consistent with the Model Proxy backend fallback, so entitled customers are no longer blocked. |
W-24128912 |
The Total Managed Spend, Total Spend on Agents, and Potential Savings values on the Optimization page now roll up correctly into the millions. |
W-24149371 |
Policy descriptions for the Tool Mapping, MCP Tools Progressive Disclosure, and Request Compression policies no longer contain typos and grammar errors. |
W-24160887 |
The Cost Management tab on an agent’s detail page now shows the correct optimization policy count and format. |
W-24161316 |
The Policy Violation Count graph on the Performance tab now displays data. |
W-24216820 |
Drill-downs on the Performance page now return data even when the environment filter isn’t selected. |
W-24250463 |
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
Installing the Slack app now succeeds when a previous session wasn’t cleared, instead of failing. |
W-23754100 |
Policy templates no longer return a proxy error. |
W-23836725 |
The Cost Management tab no longer renders blank. |
W-24007593 |
The policy-count column label is now consistent across the agent, model proxy, and MCP server dashboards. |
W-24021273 |
Applying agent optimization policies from the Optimizations tab in Ask MuleSoft no longer fails silently. |
W-24026346 |
Applying the MCP Tools Progressive Disclosure optimization policy in Ask MuleSoft no longer gets stuck in a loop. |
W-24027064 |
Managing model wallets through the MuleSoft Agent no longer requires you to provide an environment ID. |
W-24027144 |
Model wallets now appear in the model proxy route editor for organizations that have more than one environment. |
W-24043182 |
The Tokens Saved column on the model proxy Optimizations tab now shows actual values instead of always showing 0. |
W-24054184 |
Budget Management now includes an environment switcher, so you can view budgets across all your environments instead of only one. |
W-24060216 |
The Organizations filter on the MCP server and agent catalogs now shows the correct count and pagination, applies the expected checkbox behavior, and no longer shows a stale empty state when you open it from a deep link. |
W-24063692 |
You can now connect the enhanced experience to AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault so API keys and other credentials stay in your secrets manager. MuleSoft stores only metadata, such as secret names and paths, not the secret values. It reads the secret from your vault when a model proxy or other service needs it.
For more information, see Using Credentials Stored in External Vaults.
You can now contain a rogue AI agent before it leaks data, takes unauthorized actions, or runs up costs. Stop that agent’s requests from reaching your models, then restore access if the containment was a false positive.
For more information, see Detect and Contain Rogue Agents.
Cost Management now includes budget management. Set spending budgets for your model wallets, track spend against each budget, and manage budgets across providers and models from the Budgets tab.
For more information, see Budgets Tab.
The Cost Management Optimizations page now includes an Agents tab, so you can review token usage and optimization opportunities for your agents alongside model proxies and MCP servers.
For more information, see Filter and Search.
You can now create, edit, delete, and list model wallets, which allocate token budgets that are granted only when a request’s claims match the wallet’s required claims. Manage model wallets from the UI or through the MuleSoft Agent.
For more information, see Capping Spend for Callers of Model Proxies.
You can now edit instances for model proxies, APIs, agents, and MCP servers from the service detail page or the instance detail page, without switching to Anypoint Platform.
Model Proxy now supports semantic caching, TLS security for provider connections, external vault–based provider authentication, and the Model Proxy Request Compression policy.
For more details about updates to model proxy, see Model Proxy Release Notes.
MCP Bridge now exposes tool output schemas as part of the MCP specification, so you can connect servers built with MCP Bridge to Agentforce.
These SaaS connectors are now available in the Trusted MCP catalog: Wix, WordPress.com, Hootsuite, Descript, Intercom, Front, and LiveChat.
You can now create an A2A bridge to make a non-A2A agent A2A-compliant so that Agent Fabric can discover, govern, and orchestrate it alongside native A2A agents.
For more information, see Make an Agent A2A-Compliant
You can now use OAuth 2.0 Authorization Code for Microsoft Copilot Studio scanners to create, authorize, and test the provider connection before you continue scanner setup.
For more information, see Microsoft Copilot Studio OAuth Authorization.
You can now apply universal policies to your API instances and manage the resulting native policies. A universal policy is defined once and applied as the correct native policy on each supported gateway.
For more information, see:
API scanners now write policies from these provider platforms: Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in Portfolio > APIs > Policies.
For more information, see:
You can now track remediation and scan status in the Akamai Security Findings table on the Conformance tab.
For more information, see Track Remediation and Scan Status.
Cost Management optimization for MCP servers now includes policy recommendation cards with an Apply action, a sortable potential-savings column, savings framed in dollars per month, applied policies grouped by category, and a benchmark of the top MCP servers across the top models.
The Optimizations and Budgets dashboards now include a toggle to switch between dollar and token views.
MCP Bridge overview pages now group tools by the source API they were generated from, with a link to each API’s Exchange page.
MCP Bridge tool editing now includes a resource filter and instance-type badges, and you can add a TLS context and customize HTTP request mappings on a deployed MCP server.
You can now configure inbound and outbound TLS contexts when you create or modify an MCP Bridge, and Model Proxy now supports TLS context configuration for upstream connections.
You can now edit a model proxy’s deployment configuration inline, including its base path, gateway target, and consumer endpoint, with a warning when a change requires redeployment.
The Portfolio Filters menu now includes an Organizations group, so you can narrow the catalog to specific business groups and hide public MuleSoft catalog assets.
MuleSoft for Teams is now available as a limited availability feature. Install the MuleSoft for Teams app to interact with MuleSoft directly from your Microsoft Teams tenant, receive platform alerts in channels, and use MuleSoft Agent to list APIs, view MCP servers, check governance, and perform other management tasks. To request access, contact your account executive.
For more information, see Integrate the Enhanced Experience with Microsoft Teams.
The MuleSoft app for Microsoft Teams is now available in additional regions.
The MuleSoft Agent in Slack and Microsoft Teams now uses a refreshed set of cards for listing and viewing services, instances, and policies, and for applying a policy.
You can now filter your alerts and bulk-assign a Microsoft Teams channel as the delivery destination, with a confirmation step that lists the affected alerts.
When you ask the MuleSoft Agent to do something it doesn’t have a tool for, it now explains what it can do and offers to report the limitation.
MuleSoft Agent semantic search is recalibrated to return more accurate and relevant results.
Portfolio, service detail, instance detail, and policy pages load faster.
In a model proxy route, the Model field is renamed to Request model override, and Not applicable is renamed to Use model from request, to clarify that the field overrides the model specified in the incoming request.
The MuleSoft Agent panel is now hidden by default unless the MuleSoft Agent feature is enabled for your organization, and it’s hidden in trial accounts. Previously, the panel could appear for users who couldn’t access the feature.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
The MuleSoft Agent now returns results when you search for assets by type, instead of returning none. |
W-23149216 |
The MuleSoft Agent no longer returns a "No generations found in stream" error in the agent panel, Slack, and Teams. |
W-23927589 |
Switching to a child business group now returns correct results for the MuleSoft Agent in Microsoft Teams. |
W-23927098 |
Your business group selection is now preserved when you refresh the page or open the enhanced experience in a new tab. |
W-23444044 |
Installing and uninstalling the MuleSoft Slack app now works correctly. |
W-23632725 |
A clearer error message now appears when a user who isn’t an organization admin tries to connect Slack to Anypoint Platform. |
W-23360453 |
MuleSoft Agent notifications now deliver to Microsoft Teams instead of failing with an SSL error. |
W-23649227 |
Reinstalling the MuleSoft app in Microsoft Teams now recovers automatically from an installation conflict, matching Slack behavior. |
W-23651771 |
You can now connect Microsoft Teams to a second organization that uses the same Microsoft Entra tenant. |
W-23972001 |
Notifications now display the tenant ID instead of the MuleSoft organization ID. |
W-23902550 |
Toast messages are no longer truncated in the notification list. |
W-23902562 |
Testing the connection to an unreachable or invalid MCP server URL now returns a clear validation message instead of a server error. |
W-23480369 |
MCP server detail pages now show connected APIs, because connection metadata is preserved on MCP server upstreams. |
W-23748233 |
Creating a model proxy from a child business group no longer redirects you to the parent business group. |
W-23930690 |
The topics and model fields are now populated when you edit an existing model proxy that uses semantic caching. |
W-23792167 |
The Omni Gateway dropdown in the model proxy wizard now lists all gateway targets instead of only the first page. |
W-23845232 |
Permissions are now consistent between the model proxy gateway and route-configuration APIs. |
W-23845221 |
The Fallback model dropdown in the model proxy route editor no longer renders empty when a model wallet is enabled. |
W-23996495 |
The provider badge for Amazon Bedrock AgentCore now displays correctly. |
W-23995654 |
The Smart Response Trimming payload optimization policy now saves a complete model proxy URL. |
W-23561570, W-23956373 |
Payload optimization opportunities now appear for instances whose average token usage doesn’t cross the display threshold. |
W-23653988 |
Testing credentials for an OpenAI model proxy in the payload optimization policy now works. |
W-23688845 |
The Discovered tile on the home page no longer over-counts forked MuleSoft public templates. |
W-23630949 |
The agents catalog count no longer includes agent-network rows, so the count matches the assets shown. |
W-23631818 |
The Kong Gateway scanner now detects gRPC and GraphQL protocols and assigns the correct service type for these services. Services that use other protocols are registered as service type REST for now. MuleSoft plans to support more protocols in a future release.
For more information, see general::exp-scanners-add-from-providers.adoc#kong-gateway-scanner-protocol-to-asset-type-mapping.
The release addresses this enhanced MuleSoft experience issue:
| Issue Resolution | ID |
|---|---|
The Expose as MCP Server action now appears for APIs that have a deployable instance, even without a configured consumer endpoint. |
W-23922779 |
Playgrounds are now available for APIs and MCP servers. Use the Playground tab on a service detail page to explore endpoints and tools, configure and send requests, and inspect responses without leaving the enhanced experience.
For more information, see Testing Services with Playgrounds (Beta), Testing APIs in the API Playground (Beta), and Exploring MCP Server Tools in the MCP Playground (Beta).
The Akamai scanner is now available to map external security findings to the right services in Portfolio. Add the scanner to scan APIs, surface security findings, and apply governance strategies from the portfolio. The scanner doesn’t import or register third-party services. It correlates risk scores, findings, and incidents in one governance workflow.
For more information, see Correlating Risk Using Akamai API Security and Working with Governance Strategies.
Additional Trusted MCP server SaaS integrations are now available, and ready-to-use MCP client configuration snippets help you connect popular MCP clients faster.
Model Proxy now supports the Anthropic API format and native Anthropic models.
API scanners now read policies from these provider platforms: Amazon API Gateway, Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in Portfolio > APIs > Policies.
After connecting to a third-party API gateway provider, you can govern discovered APIs through the same governance workflow used for Anypoint Platform APIs. This enables unified governance across multiple gateway platforms.
For more information, see:
The Scanner details page now includes an Activity Log with a real-time timeline of scan progress events.
For more information, see Viewing Scanner History and Settings.
MCP Bridge now lets you edit tool input schemas, customize tool HTTP request mappings and headers, and expose tool output schemas as part of the MCP specification.
Cost Management now lets you edit optimization policies and is available from the Ask MuleSoft sidebar.
The LLM proxy credential test now distinguishes between credentials that can’t be verified and credentials that are invalid.
LLM Proxy is now renamed to Model Proxy.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
The MCP server creation success screen now displays a persistent runtime authentication warning banner instead of stacked notifications. |
W-22323999 |
Agent detail policy views no longer show a misleading "No instances covered" message for environment types that have no instances. |
W-22416846 |
Portfolio catalog and entity pages now load faster and filter more reliably. |
W-22580671 |
The Anypoint MCP Bridge now returns tool input schemas in valid JSON Schema format in |
W-22602876 |
Platform MCP server tools now match filter values to stored display labels, returning correct results. |
W-22850282 |
The Apply Policy agent action now displays available policies immediately instead of showing none during an initial delay. |
W-23011916 |
The agent no longer directs you to a nonexistent automated policy creation page. |
W-23012045 |
The agent no longer gets stuck on the Environment field when prefilling a governance strategy form. |
W-23091457 |
The Ping operation now works correctly in MCP Bridge. |
W-23128311 |
Cost Management now displays metrics for Twilio MCP server instances. |
W-23141551 |
API catalog filter options now include values from all assets instead of only the first page of results. |
W-23330370 |
Long LLM responses are no longer dropped mid-stream. |
W-23366770 |
The policy version selector on the policy configuration page now lists versions in order. |
W-23385993 |
Cost Management now surfaces Payload Optimization opportunity cards even when the Payload Optimization policy is not yet applied. |
W-23402200 |
Correlation policies now apply correctly to instances. |
W-23470169 |
Cost Management policy names no longer display underscores. |
W-23475812 |
The MuleSoft Agent prompt now works for users who are granted agent permission only in a child business group. |
W-23478614 |
The MCP server creation wizard now shows an accurate message when the blocker is a missing Exchange permission. |
W-23495332 |
Cost Management Payload Optimization Smart Response Trimming now works regardless of sub-policy order. |
W-23515804 |
Notification labels now match Anypoint Platform. |
W-23522019 |
The agent no longer rejects legitimate platform questions as off-topic. |
W-23528364 |
The agent no longer loops when discovering assets that include nested environment fields. |
W-23564370 |
Cost Management now uses the latest policy version for Trusted MCP servers. |
W-23574980 |
Cost Management now surfaces Payload Optimization opportunities in instance modals even when projected savings are below the display threshold. |
W-23632337 |
The new Payload Optimization policy page lets you configure token-reduction strategies, including payload sanitization and TOON encoding, as toggleable sub-policies.
Cost Management now surfaces Payload Optimization sub-policies as opportunity cards, so you can act on top token-savings recommendations directly from the Cost Management page.
The new MCP Tools Progressive Disclosure policy enables you to reduce context window token cost by exposing tools on demand through search. Apply the policy Cost Management.
Instance detail pages now display the consumer endpoint URL, including the base path, so you can copy a callable URL without switching to Anypoint Platform.
Tool Mapping policy configuration now includes a version selector, so you can update the policy to a new version.
Applied policies now display a "New version available" indicator when a newer version is available.
The model proxy overview now shows the configured fallback route and semantic prompt guard as summary cards, so you can review them without entering edit mode.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
The MCP server Create & Deploy button now displays progress notifications instead of internal provisioning steps. |
W-22477443 |
The monitoring summary page now loads successfully and no longer times out because of backend connectivity failures. |
W-22561882 |
MCP server creation no longer pre-selects a gateway without a public URL, preventing validation errors during review. |
W-22569213 |
MCP server detail pages now open correctly even before the asset is fully indexed, instead of redirecting to the MCP server list. |
W-22668860 |
Name and path validation is improved during MCP server creation. |
W-22730633 |
Policy views for externally managed gateway instances now return an empty policy set instead of a 404 error. |
W-22850289 |
The Run discovery scan quick action in the agent panel now performs the same scan as the Run discovery scan button on scanner pages. |
W-22855741 |
MCP tool input schemas now display complete information. |
W-22903101 |
Long text entered in the agent panel input box now stays within its container. |
W-23012031 |
The Support Credentials toggle in Cross-Origin Resource Sharing policy configuration is now enabled, matching earlier behavior. |
W-23050595 |
Health Check policy configuration now routes you to the alert builder to create an alert after the policy is applied. |
W-23050597 |
Injection Protection policy configuration now provides a multi-select dropdown for built-in protections instead of a free-form text field. |
W-23050599 |
Policy configuration forms with nested fields no longer add an empty row that caused save errors. |
W-23050623 |
Navigation from the agent panel to a specific agent’s detail page now works correctly. |
W-23091579 |
Availability drill-downs now display the availability metric instead of the reliability metric. |
W-23111937 |
Time-series chart drill-downs now display the time bucket you select instead of an adjacent one. |
W-23111946 |
Agent portfolio search now returns agents that also appear in the main UI search. |
W-23113003 |
Tool-mapping descriptions are no longer duplicated when a tool’s summary and description match. |
W-23130198 |
Agent responses now display consistently in chat history. |
W-23131703 |
Cost Management token-savings projections in the instance detail modal now update to match the selected timeframe instead of always using the 30-day period. |
W-23140133 |
The trusted MCP wizard footer now adjusts correctly when the sidebar is collapsed. |
W-23176162 |
Cost Management tool optimization now displays an error message when your organization lacks Agentforce access instead of failing silently. |
W-23178835 |
Acronis test-connection operations now succeed by using the correct tenant filter. |
W-23181533 |
Editing a policy no longer disables or unchecks unrelated fields whose names end in |
W-23186039 |
Model Based Routing policy configuration now displays the selected version after you change and save it. |
W-23200921 |
Cost Management tooltips now render with a solid background for better readability. |
W-23312200 |
Cost Management now displays estimated saved tokens correctly when optimization strategies are active. |
W-23319697 |
Model proxies now supports multiple routes to the same LLM provider and can filter requests to different routes with headers.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
Manual API registration now processes uploaded .zip files without errors. |
W-22441824 |
Manual API registration now processes uploaded JSON and YAML files without server errors. |
W-22441846 |
Portfolio page headers and toolbars now remain fixed at the top when scrolling. |
W-22454943 |
Newly created API instances now appear immediately in the instance list. |
W-22461347 |
Basic Authentication policy password fields now mask input correctly. |
W-22476294 |
Slack Agent now processes Omni Gateway requests without errors. |
W-22518488 |
Pre-selected paths in MCP Server creation no longer display validation errors during review. |
W-22599092 |
Slack Agent responses now focus on available actions instead of describing unavailable creation workflows. |
W-22642526 |
MCP transcoding operations now correctly handle body literals without affecting upstream policies. |
W-22642906 |
Gateway detail page links now redirect to Anypoint Runtime Manager with the correct environment scope. |
W-22708401 |
Outbound OAuth 2.0 Credential Injection policies now allow setting Client ID and Secret. |
W-22815084 |
Policy listing views now clearly distinguish between inbound and outbound policies. |
W-22923681 |
Model proxy asset creation now handles Exchange API responses without HTTP 502 errors. |
W-22927281 |
MCP Server tool lists now return all available tools without truncating results at 512 items. |
W-22928504 |
Portfolio page provider filters now display all configured providers instead of a static list. |
W-22928563 |
Portfolio page filters now handle large result sets without returning empty results. |
W-22928667 |
OAuth 2.0 test connection operations now work correctly when creating an MCP server. |
W-22965458 |
API specification overviews for gRPC APIs now populate correctly in the India region. |
W-22966440 |
A2A PII Detector policy configuration now supports multi-select for PII types. |
W-23050572 |
MCP PII Detector policy configuration now supports multi-select for PII types. |
W-23050575 |
LLM PII Detection policy configuration now supports multi-select for PII types. |
W-23050578 |
Model Based Routing policy configuration now includes Match Headers and isFallback Entry fields. |
W-23050585 |
Client ID Enforcement policy configuration now displays Client ID Expression and Client Secret Expression fields when Custom Expression is selected. |
W-23050592 |
JWT Validation policy configuration now includes JWT Signing Key Length, conditional JWT Key fields, and Client ID Expression. |
W-23050601 |
Credential Injection API Key policy configuration now displays auth-type-dependent fields for custom headers, API keys, and client credentials. |
W-23050605 |
Credential Injection OAuth 2.0 policy configuration now displays grant-type-dependent fields for Client Credentials and Password grant types. |
W-23050608 |
OAuth 2.0 OBO Credential Injection policy configuration now displays all grant-type-dependent fields. |
W-23050613 |
Agent registration workflow now uses correct naming conventions. |
W-23064092 |
MCP Server creation now displays clear, actionable error messages when credential validation fails. |
W-23073090 |
Acronis credential test operations now work correctly with network allowlist configurations. |
W-23085376 |
Public Agent detail pages no longer display delete icons. |
W-23090929 |
POST tools created from MCP bridge connections now correctly include all input parameters. |
W-23128385 |
The MuleSoft Agent now displays correctly for users who have been enabled in child business groups. |
W-23182443 |
Notifications are now available, allowing you to configure and receive alerts for service health and governance events.
For more information, see Configuring Notifications for Alerts.
MuleSoft Agent is now available. Manage your MuleSoft environment with MuleSoft Agent, an agentic experience available in the control plane. Use MuleSoft Agent to create scanners, apply policies, deploy instances, and perform other management tasks. To request access, contact your account executive.
For more information, see Using the MuleSoft Agent.
MuleSoft for Slack is now available. Install the MuleSoft Slack app to interact with the MuleSoft Platform directly from your Slack workspace, send platform notifications to Slack channels or direct messages, take platform actions, and ask questions about your MuleSoft organization.
For more information, see Integrate the Enhanced Experience with Slack.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
Inactive instances now display correctly across both pipeline and summary views. |
W-22456216 |
Instance detail pages now display environment names correctly instead of showing only environment types. |
W-22455820 |
Instance detail page headers now display correctly with proper styling and element positioning. |
W-22455880 |
Governance strategy deletion now completes successfully without returning errors. |
W-22476104 |
The MCP Server creation flow no longer displays premature "select at least one tool" warnings during loading or when no operations exist. |
W-22490327 |
MCP Server creation now displays helpful error messages when incorrect credentials are provided. |
W-22570827, W-22570738 |
Connected asset graph links on agent pages now navigate directly to entity detail pages instead of list pages. |
W-22571289 |
Cost Management recommendation cards now display in strict descending order by projected savings. |
W-22586604 |
Text overflow issues on MCP Server creation pages are resolved. |
W-22598973, W-22622184 |
Auto-generated MCP tool names now follow snake_case convention and use operation names instead of API asset prefixes. |
W-22601645 |
The Continue button now enables correctly after editing optimized tool names and descriptions in Tool Mapping policy imports. |
W-22603960 |
The MCP Tool Response Sanitization policy now displays values that match Anypoint settings. |
W-22692504 |
Chat input fields in Cost Management now handle long prompts without overflowing the container. |
W-22692107 |
Consumer endpoints now display correctly and no longer intermittently show implementation URLs. |
W-22696329 |
Gateway URLs in MCP Server creation now update correctly instead of remaining stuck at default demo URLs. |
W-22696327 |
Scan summaries now correctly display skipped services in provider scan results. |
W-22701129 |
Cost Management optimization estimations now correctly check input schemas. |
W-22709243 |
Credential input fields in the MCP Server wizard now display correct validation messages. |
W-22730686 |
Azure API Management providers now display correctly in the provider listing. |
W-22730614 |
You can now delete MCP assets from the catalog when they have zero instances. |
W-22732824 |
Model proxy Bedrock routes now correctly clear empty session tokens when switching from STS to long-term IAM credentials. |
W-22769399 |
Scanner deletion operations now complete cleanly without displaying stale scanner data. |
W-22779340 |
Cost Management optimization operations now display loading indicators correctly for individual rows instead of all rows. |
W-22781792 |
Consumer endpoint URLs for trusted MCP servers now include the correct |
W-22782195 |
Read-only operation selection in MCP bridge SaaS actions now correctly deselects PUT operations. |
W-22784169 |
The JWT Validation policy configuration form now includes the JWT Key input parameter. |
W-22795041 |
Service catalog counts now display consistently between the UI and MCP server counts. |
W-22795809 |
Provider pages now reload correctly when switching Business Groups. |
W-22795416 |
Provider filters on the Agents portfolio page now return correct results for all providers including Amazon Bedrock AgentCore and Azure AI Foundry. |
W-22910173 |
HTTP Basic Authentication configuration for Client ID Enforcement policies now works correctly. |
W-22923781 |
You can now edit policy configurations for all policy types. |
W-22923643 |
Rate Limiting policy search now works as expected. |
W-22923811 |
OAuth2 OBO Credential Injection now works correctly for outbound policies. |
W-22924163 |
Cross Origin policy forms now properly disable the Support Credentials option when applicable. |
W-22924051 |
Tool response size limits now prevent oversized responses from exceeding client token limits. |
W-22947243 |
Scanner connection tests for Vertex AI now return descriptive error messages on failures. |
W-22947245 |
API instance upstream URLs now update correctly when editing trusted MCP server configurations. |
W-22971120 |
Monitoring and performance modules now load correctly without modularity errors. |
W-22999188 |
The All Versions filter label now displays correctly on monitoring pages instead of showing MISSING_KEY errors. |
W-23003583 |
MCP bridge instances now display availability status correctly. |
W-23003437 |
Asset search now validates query parameters correctly and no longer accepts empty queries. |
W-22962129 |
Agent and MCP detail pages now display enriched metadata correctly. |
W-22992220 |
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
The Performance page now displays monitoring data correctly for organizations in the India cloud. |
W-22997947 |
Monitoring data now resolves to the correct environment when organizations contain multiple environments of the same type. |
W-23007726 |
The Instances column header now displays Env Type instead of Environment. |
W-22418037 |
The Edit action now appears in the action menu on MCP Server detail pages in EU, Japan, and Canada clouds. |
W-22693560 |
CloudFront URL access for file downloads now works correctly in Japan and Canada clouds. |
W-22686958 |
This release includes security updates and improvements to the enhanced MuleSoft experience.
The release addresses these enhanced MuleSoft experience issues:
| Issue Resolution | ID |
|---|---|
You can now deploy, edit, and delete MCP servers that share the same name. |
W-22603005 |
Auto-generated MCP tool names no longer contain spaces, ensuring compliance with the MCP specification. |
W-22816476 |
You can now open service detail pages from the Services catalog while viewing the root Business Group context. |
W-22696491 |
Governance Insights reports now display policy rulesets and instances correctly. |
W-22710201 |
The Environment filter on the Gateways catalog page now correctly filters the displayed gateways by the selected environment. |
W-22778035 |
The Provider filter on portfolio pages (Agents, APIs, MCPs) now correctly returns services associated with the selected provider. |
W-22815822 |
The Vitest library is upgraded to 4.1.8 to address a reported security vulnerability. |
W-22777847 |
Automated policies configured at both organization and environment levels now display correctly without duplicated policy activity. |
W-22735582 |
Policy direction (inbound or outbound) now displays correctly under application methods instead of showing generic instance policy labels. |
W-22801826 |
A cross-tenant security vulnerability that allowed unauthorized access to Kong gateway plugin configurations across organizations is resolved. |
W-22803601 |
Public MCP Server and Agent assets no longer allow unmanaged instance creation. |
W-22733185 |
MCP server provisioning status now updates more reliably while reducing unnecessary refresh cycles. |
W-22725529 |
Third-party libraries are updated to resolve reported security vulnerabilities. |
W-22618670 |
You can now manage agents, APIs, MCP servers, model proxies, and gateways from one portfolio experience, so teams can govern and operate AI integrations without switching between separate tools.
For more information, see Enhanced MuleSoft Experience and Enhanced MuleSoft Experience Overview.
You can now add services through provider-based discovery or manual registration, so teams can onboard both cloud-managed and custom services faster.
For more information, see Adding Services to Your Portfolio, Create a Scanner for Provider Services, and Register Services Manually.
You can now create MCP servers by selecting source systems and publishing tools and resources for MCP clients, so you can more easily expose existing APIs and SaaS systems through MCP workflows.
For more information, see Create MCP Servers with MCP Bridge.
You can now add semantic services with Basic and Advanced scale models, so LLM-driven requests route with improved context awareness as traffic grows.
For more information, see Configuring Semantic Routing Services.
You can now apply governance strategies across supported service types, so teams can enforce conformance and cost controls more consistently.
For more information, see Create Governance Strategies and Viewing Service Details in the Portfolio.
Scanner operations now support lifecycle workflows for running, pausing, editing, and deleting scanners, so provider discovery stays current with less manual overhead.
For more information, see Adding Scanners from Providers and Running and Managing Scanners.
Service detail pages now centralize instance creation and management workflows for supported catalogs, so teams can align deployment operations with governance and monitoring workflows.
For more information, see Creating and Managing Instances of Services and Viewing Service Details in the Portfolio.
Monitoring guidance now connects service health, detailed metrics, and token and response analysis, so responders can triage regressions faster.
For more information, see Monitoring Services in Your Portfolio, View Detailed Metrics for Your Services, and Managing Costs and Token Usage.
You can now access the experience from Anypoint Platform, direct URLs, and supported coding assistants, so teams can work from existing workflow surfaces.
For more information, see Get Started with the Enhanced Experience Connect the Enhanced Experience to Claude Desktop.
Service detail pages now clarify tab availability by service type, so operators can more easily find instance, governance, and conformance data by catalog.
For more information, see Viewing Service Details in the Portfolio.