Please note that when using MCP Bridge V1, in the Anypoint API Manager UI under policies section for your MCP Bridge Instance, customers will not have option in the UI to re-order the policies.
By default, when a MCP Bridge Instance is created, there are policies that gets created automatically, for example - MCP Support, MCP Schema Validation Policy and MCP Transcoding Router Inbound policies
Now, Let's say if a customer wants to use some authentication policy to protect this MCP Bridge instance, for example - Client ID Enforcement Policy. Once you apply this policy from UI, you'll see it as added in the last order.
Now, if you want to re-order this policy from UI, once you click on re-order policies, the policies don't appear and a warning shows on UI saying that policies can't be re-ordered.
Customers need to use the below REST API Calls to re-order the polices for your MCP Bridge Instance in MCP Bridge V1
1. Generate a bearer token by following the instructions in the below articles
>> https://help.salesforce.com/s/articleView?id=001116775&type=1
>> https://help.salesforce.com/s/articleView?id=001115323&type=1
2. Use the GET Policies API Manager API call to retrieve the complete policy details with IDs for your API instance.
make the get policies api call for your api instance to get the complete policy details with ids, use the below api call to get the details
>> https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%236419/
3. Make a PATCH API call to re-order the policies for your API instance by specifying the desired order.
>> https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%236454/
4. Verify the re-ordered policy sequence by making the GET Policies API call again.
NOTE: UI may not reflect the updated sequence in MCP Bridge V1.
Please also find the sample app calls for the same and replace the orgid, envid and instance id values with your actual values on your end.
GET Policies call -
curl --location 'https://anypoint.mulesoft.com/apimanager/api/v1/organizations/{orgId}/environments/{envId}apis/{apiInstanceId}/policies?fullInfo=false' \
--header 'Authorization: Bearer XXX'
PATCH Policy re-order call -
curl --location --request PATCH 'https://anypoint.mulesoft.com/apimanager/api/v1/organizations/{orgId}/environments/{envId}/apis/{apiInstanceId}/policies' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer XXX' \
--data '[
{
"id": XX,
"order": 1
},
{
"id": XX,
"order": 2
},
{
"id": XX,
"order": 3
},
{
"id": XX,
"order": 4
},
{
"id": XX,
"order": 5
},
{
"id": XX,
"order": 6
}
]'
NOTE: Replace the orgId, envId, apiInstanceId and bearer token values with the actual values of your values
Also, the id values that needs to be passed in the PATCH call will be retrieved and present from the Get Policies call
https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/
https://docs.mulesoft.com/api-manager/latest/create-instance-task-mcp-bridge
005321695

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.