For IT and AI leaders

Roll out AI assistants fast, with access under control.

Give teams the AI assistants they want, connected to enterprise data. Reuse approved connections and a common access runtime as you bring on more teams, with each task governed and its activity recorded.

The challenge

Adding an assistant shouldn’t mean starting over.

Connecting assistants to systems independently repeats credential setup, access controls, and security reviews. Agents also choose their next query or action as work unfolds, so access controls must run inline at runtime. IT needs a common foundation for both rollout and oversight.

Reuse approved connections across assistants

Set up source connections in MarcoPolo and make them available through supported assistants. Add MarcoPolo once in each assistant; each person signs in under their own identity and permitted access.

secure connectivitylive
Caller · your assistants
ClaudeChatGPTCursor
one mcp connection
MarcoPolo runtime

Each person signs in as themselves

data stays in place
Salesforcesales_read
Snowflakeanalytics_ro
Postgresapp_read
Jiraissues_read

Expand from the first team’s task

Start with a useful task across existing systems. Give the next team access to approved connections with the permissions and task restrictions appropriate to its work.

secure connectivitylive
Caller · one team, one task
financeclaude.ai
existing systems
MarcoPolo runtime

Data stays in its source systems

data stays in place
Salesforcesales_read
Snowflakeanalytics_ro
Postgresapp_read
Jiraissues_read

Give security a consistent basis for review

Use the same runtime for credential protection, inline access controls, and activity records. Reuse the architecture and evidence as you assess each new rollout.

auditabilitylive
assistantclaude.aiuseramina@acmeconnectionsalesforcepolicysales_readoutcomeallowed
rollout.reviewruntime

One runtime to review, then extend to more teams

req#a91cactivity history · export
From first team to wider rollout

Start with one team. Reuse the foundation.

Make the first deployment useful, then use it to establish how the next team gets access and how IT reviews its activity.

  1. Choose a task and its boundaries

    Identify the team, its preferred assistant, the systems it needs, and the records and actions the task requires. Agree with security on what stays out of scope.

  2. Connect, grant access, and review

    Provision the source connections, grant access to the right people, and configure task restrictions. Run the task and inspect the access history with IT and security.

  3. Extend to another assistant or team

    Reuse approved connections through the next supported assistant. Review the new team’s permissions and task scope while keeping the same enforcement and audit approach.

What carries forward

A foundation for the next rollout.

Connections
Approved access to the systems already in place.
Controls
Task restrictions enforced within each identity’s permissions.
Oversight
A common activity history for IT and security to review.

Each new team keeps its own access boundaries. Reusing a connection does not grant everyone the same data.

01 / Sales

Prepare an account brief.

The task

“Summarize open deals and support issues for my region’s accounts.”
Under whose authority
A sales manager, within their assigned region.
Connected systems
CRM + support system

The agent can prepare the brief with the business data it needs. Personal contact details and record changes stay outside its scope.

  1. Secure connectivity

    Read current account, deal, and issue data directly from the CRM and support system. Keep credentials out of the agent’s model context.

  2. Access control

    MarcoPolo applies access controls on each request, enforcing the manager’s enterprise permissions and the agent’s task-specific policy for the account brief.

    Allowed
    Read account names, deal values, and issue status for the assigned region.
    Blocked
    Read other regions’ accounts or customer email addresses and phone numbers; change CRM or support records.
  3. Auditability

    Record the agent’s reads across both systems under the manager’s authority. Review which data it accessed and whether requests stayed within the approved scope.

The next assistant uses the same approved access.

A sales manager can prepare this brief in one supported assistant, then use another through MarcoPolo with the same approved connections and task policy. A manager in another region remains limited to that region. IT reviews activity through the same runtime.

See more examples →
Deployment & integration

Fits in your environment.

Architecture, security controls, and deployment documentation to support your security review.

Your cloud

Deploy in your own cloud or on premises, in the region you choose, to meet your data residency, security, and compliance requirements.

Your identity provider

Connect your enterprise identity provider for single sign-on. Keep identity and application access managed through your existing IT controls.

Your policy and governance framework

Keep source permissions in the systems that own them, including Snowflake and Databricks. Configure additional task restrictions in MarcoPolo; they can narrow access but cannot expand those permissions.

Your logging and SIEM

Bring agent activity into your logging and SIEM tools through OpenTelemetry. Trace identity, connection, action, and outcome alongside your existing operational records.

Security brief and compliance documentation on request · Trust & security →

Choose the first team to roll out.

Bring the assistants your teams want, the systems they need, and your access requirements. Plan the first deployment and how the next team will build on it.