Executes a scanner and views discovered services (such as AI agents, MCP servers, and API metadata). Use when running a scan, checking scan status, viewing scan history, reviewing discovered services from external platforms, or importing services into Anypoint Exchange.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Executes a scanner configuration to discover services from an external platform, then retrieves the scan results including all discovered services. This is useful for manually triggering scans or reviewing what was found.
What you'll build: A complete scan execution with visibility into discovered services ready for publication to Exchange.
Before starting, ensure you have:
Trigger the scanner to start discovering services from the configured external platform.
What you'll need:
Action: Start the scan execution.
api: urn:api:agent-scanner-configuration-service
operationId: executeWorkflowFromConfiguration
inputs:
organizationId:
from:
api: urn:api:access-management
operation: getOrganizations
field: $.id
name: currentOrganization
description: Your organization's Business Group GUID
scannerConfigurationId:
from:
api: urn:api:agent-scanner-configuration-service
operation: getScanConfigurations
field: $.content[*].id
description: The scanner configuration to execute
outputs: []What happens next: The scan starts asynchronously. You'll receive a 202 Accepted response. The scan runs in the background, discovering services from the external platform.
Common issues:
Check the status of your scan by retrieving the run history.
What you'll need:
Action: Retrieve the list of scan runs to find your execution.
api: urn:api:agent-scanner-configuration-service
operationId: getScannerRunHistory
inputs:
organizationId:
from:
variable: organizationId
description: Same organization ID as Step 1
scannerId:
from:
variable: scannerConfigurationId
description: The scanner configuration ID (used as scanner ID)
page:
value: "0"
description: Page number (0-indexed)
size:
value: "20"
description: Number of results per page
outputs:
- name: scanRunId
path: $.content[0].id
description: The most recent scan run ID
- name: scanStatus
path: $.content[0].status
description: Current status (RUNNING, COMPLETED, FAILED, ABORTED)
- name: startedAt
path: $.content[0].startedAt
description: When the scan started
- name: endedAt
path: $.content[0].endedAt
description: When the scan completed (null if still running)What happens next: You receive a paginated list of scan runs sorted by most recent. Check the status field to see if your scan is still RUNNING or has COMPLETED.
Common issues:
Once the scan completes, retrieve the list of discovered services (staging assets).
What you'll need:
Action: Get the staging assets discovered during the scan.
api: urn:api:agent-scanner-configuration-service
operationId: getStagingAssetsByScanRunId
inputs:
scannerId:
from:
variable: scannerId
description: The scanner ID
scanRunId:
from:
variable: scanRunId
description: The scan run ID from Step 2
page:
value: "0"
description: Page number (0-indexed)
size:
value: "0"
description: Use 0 to get all results without pagination
outputs:
- name: assetId
path: $.content[*].assetId
description: The asset ID in Exchange (if published)
- name: assetName
path: $.content[*].name
description: Name of the discovered service
- name: stagingStatus
path: $.content[*].stagingStatus
description: Status (NEW, EXISTING, PUBLISHED, FAILED)
- name: operationPerformed
path: $.content[*].operationPerformed
description: What action was taken (CREATE, UPDATE, DELETE, SKIP)What happens next: You receive a list of all services discovered during the scan, including their names, descriptions, and publication status.
After completing all steps, verify:
Your scan execution has produced:
Scan Run Record
Discovered Services
Now that you've seen the discovered services:
Symptoms: Scan status remains RUNNING for an extended period
Possible causes:
Solutions:
Symptoms: Scan completes but staging assets list is empty
Possible causes:
Solutions:
Symptoms: Scan status shows FAILED shortly after starting
Possible causes:
Solutions:
mulesoft/mulesoft-dx
4340d6c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.