What execution boundaries and permissions apply to agent-bev?

agent-bev capabilities are recorded from official registry declarations across read, write, execution, and delete permission surfaces.

agent-bev

Q: How does agent-bev map to EU AI Act Article 14 Human Oversight?

Evaluating reviewer roles and oversight controls for agent-bev requires customer deployment context. Flash Scan allows mapping operational review policies against tool capabilities.

ai.agent-bev v0.2.5

The world's largest agentic B2B hub for beer, wine and spirits. Powered by CUVEE. Trade only.

            Publisher: Model Context Protocol Registry
            License: unknown

Subject DID

            did:vos:external-reference:mcp-ai-agent-bev-bev-door
          

Publication Rights

            Publication rights decision: approved
          

What governance signals are available for agent-bev under EU AI Act oversight workflows?

agent-bev is indexed from official MCP registry observations. Static tool metadata does not establish runtime session oversight or execution safety. Connecting agent-bev to VOS Signal Mesh can support audit-readiness and verifiable evidence logging for Article 14 human-in-the-loop workflows.

Technical Capability Signals Permission Bounds

Observed execution surface across file, database, command execution, and network interfaces:

        READ
        UNKNOWN
      

        WRITE
        UNKNOWN
      

        EXECUTE
        UNKNOWN
      

        DELETE
        UNKNOWN
      

Observation Limitations & Boundaries

Static registry metadata does not verify runtime environment credentials, network isolation, or human review controls.

Governance Dimensions Source-Grounded Data

Recorded regulatory dimensions under EU AI Act, NIST AI RMF, and ISO 42001:

Exposure Profile

              unknown
            

Verification Provenance

              Source Confirmed (Official MCP Registry Anchor)
            

Contextual Risk Classification

              Insufficient Context (Requires Tenant Deployment & Jurisdiction Binding)
            

Article 14 Human Oversight Readiness

              unknown
            

Governance & Audit Observations

Observation signals recorded for agent-bev from the official MCP registry:

🇪🇺 Article 14 — Human Oversight Mapping

Evaluating reviewer roles and oversight controls requires customer deployment context. Flash Scan allows mapping operational review policies against tool capabilities.

🛡️ Article 15 — Operational Boundaries

Execution boundaries, timeout parameters, and permission scopes depend on runtime configuration within the host environment.

📜 Article 50 — Technical Transparency

Metadata disclosures and schema parameters recorded from the official registry listing under policy sp-2026-09-v1.

Run Instant Liability Gap Analysis

VOS supports governance, evidence and audit-readiness workflows. It is not legal advice and does not certify compliance by itself.

Scan Connected Tools (10s Free) ← Tools Radar