Skip to main content

What this is for

The Agents workspace is where you inspect every AI agent Guardway has discovered in your cloud accounts. For each agent you see models, tools, MCP servers, routing posture against your gateways, linked Entra ID identities when configured, and OWASP Top 10 for Agentic Applications findings. It lives at Agents in the dashboard sidebar (between Playground and Logs). The workspace has two tabs — Inventory and Findings — plus a per-agent detail view when you click a row. Org-wide totals, routing percentages, and finding breakdowns live on Dashboard → Agents — use Open Agents workspace from that tab to jump here.
Discovery is configured under Settings → Integrations. You will not see agents until at least one cloud AI integration is connected and the first sync completes.

Connectors

ProviderStatusSet up under
Azure AI FoundryAvailableSettings → Integrations → Azure AI Foundry
Amazon BedrockAvailableSettings → Integrations → Amazon Bedrock
Microsoft Entra IDAvailable — identity hydration onlySettings → Integrations → Microsoft Entra ID
GCP Vertex AgentsComing soon
Azure AI Foundry and Amazon Bedrock populate the inventory. Each connector discovers agents for its cloud; the Provider column distinguishes them. Microsoft Entra ID does not add agents. It hydrates each discovered agent with execution identity (Service Principal or Managed Identity), owners, credential lifecycle, OAuth grants, and directory roles for ASI03 rules. Identity sync runs after a successful Resync on the Azure AI Foundry card (or after Test Microsoft Graph access on the Entra card). The Azure AI Foundry connector discovers both prompt agents (default in the New Foundry experience) and legacy Assistants-API agents.

Inventory

The default tab when you open Agents (URL omits tab or uses ?tab=inventory).

Toolbar

ElementNotes
Search agents…Filters the table client-side by agent name.
RefreshReloads agent and finding data from the discovery service.

Columns

ColumnNotes
AgentClick to open the agent detail view.
ProviderConnector that discovered the agent (e.g. Azure AI Foundry).
ProjectProvider-side container (Foundry project, Bedrock environment, etc.).
ModelsUp to two deployment names; +N when more.
ToolsCount of registered tools.
MCPCount of attached MCP servers; red N risky when any are high risk.
RiskWorst open OWASP severity chip plus total finding count (e.g. MEDIUM (1)). Empty when no open findings.
RoutingGateway: <name>, Bypassing gateway, or Routing unknown.
Last seenDate last observed; link icon opens the provider console when a deep link exists.
Pagination: Rows per page (default 25), Showing X–Y of Z agents.
Agents inventory table

Findings

Switch to the Findings tab (?tab=findings) for the org-wide OWASP list.

Toolbar

ElementNotes
Search findings…Filters by finding title, description, rule id, or agent name.
All categoriesDefault, or filter to one ASI code (ASI01ASI10). The dropdown lists full names; the table Category column shows the short code only (ASI03, ASI02, …).
All severitiesDefault, or Critical, High, Medium, Low, Info.
RefreshReloads findings.

Columns

Sorted by severity (highest first), then category, then rule id.
ColumnNotes
SeverityColor-coded chip.
CategoryASI code chip (short form in the grid).
AgentLinks to agent detail. Shows a monospaced row id if the agent was removed.
FindingRule title above, description below.
RuleStable id (e.g. asi03.shared_identity_across_agents).
Last seenDate the finding was last observed.
Empty state: No OWASP findings detected. with a green shield icon.
OWASP findings table

Agent detail

Opens when you click an inventory row. Back control: Agents. Agent name, provider · project · account label, Routing unknown / gateway badge, optional worst-severity chip and N ASI finding(s) anchor to the findings card, Open in console when raw_url is present.

Sections (in order)

SectionNotes
OWASP Top 10 findings (N)Grouped by ASI category. Remediation and Evidence collapsibles per finding; Evidence shows JSON from the rule evaluator.
Identities (N)One row per Entra principal. Display name, type chip (ServicePrincipal, ManagedIdentity, Application), link source (Foundry account managed identity, Declared in agent metadata, Assistant owner). Object id, Attached to for Managed Identities, owner count (suppressed for MIs with an attached resource), credential badges (N expired, N expiring <30d), N risky scope(s). Hidden when no identity resolved.
Models (N)Deployment name, provider kind, deployment alias, endpoint URL.
Tools (N)Name, description, kind chip.
MCP servers (N)Name, URL, transport, risk badge.
Footer: last discovered timestamp.
Agent detail with OWASP findings and Identities

OWASP Top 10 categories

Guardway maps findings to the OWASP Top 10 for Agentic Applications 2026 framework. Five categories are evaluated in this release from passive cloud metadata; the rest are deferred (Limits).
CategoryTitleEvaluated
ASI01Agent Goal HijackNo
ASI02Tool Misuse & ExploitationYes
ASI03Identity & Privilege AbuseYes
ASI04Agentic Supply Chain VulnerabilitiesYes
ASI05Unexpected Code Execution (RCE)Yes
ASI06Memory & Context PoisoningNo
ASI07Insecure Inter-Agent CommunicationYes
ASI08Cascading FailuresNo
ASI09Human-Agent Trust ExploitationNo
ASI10Rogue AgentsNo

Rule reference

RuleSeverityTriggers when
asi02.code_interpreter_presentMediumThe agent has a code_interpreter tool registered.
asi02.high_tool_countLowMore than 10 tools.
asi02.unknown_kind_toolInfoA tool kind could not be classified.
Rules below no_managed_identity_hint require Microsoft Entra ID and a resolved agent → principal link.
RuleSeverityTriggers when
asi03.no_managed_identity_hintMediumPrivileged-looking tools, no Entra principal linked, no identity in metadata.
asi03.shared_identity_across_agentsMediumSame Entra principal across multiple agents.
asi03.expired_credentialHighExpired client secret or certificate on the identity.
asi03.credential_expiring_soonMediumCredential expiring within 30 days.
asi03.long_lived_secretMediumClient secret lifetime greater than one year.
asi03.overprivileged_consentHighHigh-risk Microsoft Graph permissions on the identity.
asi03.privileged_directory_roleCriticalGlobal Administrator, Privileged Role Administrator, Application Administrator, or Cloud Application Administrator.
asi03.orphaned_principalMediumService Principal or Application with no owners (MIs exempt).
asi03.disabled_ownerMediumAll user owners disabled.
asi03.unverified_principalLowMetadata principal id does not match any tenant principal.
asi03.dormant_principalLowNo sign-in for 90+ days (AuditLog.Read.All + AAD Premium required).
RuleSeverityTriggers when
asi04.mcp_server_unpinned_urlHighMCP host outside trusted allowlist.
asi04.openapi_external_specMediumOpenAPI spec URL outside allowlist.
asi04.mcp_server_no_urlLowMCP server has no URL recorded.
RuleSeverityTriggers when
asi05.code_interpreter_presentHighcode_interpreter tool present.
asi05.shell_like_function_toolHighFunction tool matches shell/eval patterns.
RuleSeverityTriggers when
asi07.mcp_http_transportHighMCP uses http transport or http:// URL.
asi07.mcp_unknown_transportMediumTransport unknown from discovery.

Severity meanings

SeverityTypical impact
CriticalDirect path to compromise without further conditions.
HighMaterial risk under common attack paths.
MediumIncreased attack surface or reduced visibility.
LowHygiene issue.
InfoDiagnostic / connector visibility gap.

Lifecycle

Findings are created on first rule match, updated on each sync when the rule still fires, and pruned automatically when the rule stops firing. Deleting an agent in the provider removes its findings.

Gateway routing detection

Hostname of the model endpoint is compared to registered gateway URLs.
StateMeaning
Gateway: <name>Endpoint matches a registered gateway.
Bypassing gatewayDirect to upstream provider.
Routing unknownEndpoint URL not resolved (common for Foundry prompt agents).

Limits

  • One subscription (Azure) or account+region (Bedrock) per provider per organization in v1.
  • Refresh is on-demand via integration Resync; no continuous background poll yet.
  • OWASP evaluation is passive — Guardway never sends prompts to discovered agents.
  • Five ASI categories evaluated (ASI02, ASI03, ASI04, ASI05, ASI07).
  • ASI04 allowlist: until seeded, MCP hosts may all trigger asi04.mcp_server_unpinned_url.