Use cases

Real agents. Real actions. One gate.

These aren’t hypotheticals — each is a pattern shipping today, from GitHub Copilot’s coding agent to Stripe’s payment toolkit to PostHog’s SQL copilot. Pick one: every page walks the case step by step, with the real command and exactly what MCPIP returns — including the attack that gets denied.

GitHubPlatform / DevEx

Coding agents with production access

An autonomous coding agent opens PRs, runs CI, and can deploy or run migrations. The risk isn’t the code it writes — it’s the deploy hooks, CI secrets, and cloud credentials the pipeline can reach.

walk the case →
SalesforceSupport Ops / CX

Support agents that issue refunds

A support agent resolves tickets and can issue refunds, apply credits, and update the CRM. Every inbound message is untrusted input aimed at something that can move money.

walk the case →
PostHogData platform

Data agents with warehouse write access

An in-product analytics agent writes SQL, edits dashboards, and toggles feature flags against your warehouse — the pattern every analytics tool now ships.

walk the case →
Kubernetes ecosystemSRE / Reliability

Ops agents that restart services and scale infra

An on-call agent reads alerts and can restart pods, scale deployments, drain nodes, or roll back releases through cloud and orchestration tools.

walk the case →
StripeFinance Engineering

Back-office agents that move money

An agent reconciles invoices, posts journal entries, and initiates vendor payments — actions that are effectively irreversible once they clear.

walk the case →
OpenAIEnterprise IT / Security

Computer-use agents on internal apps

A computer-use agent drives a browser — clicking, typing, and filling forms across web apps, including your internal admin panels and partner portals.

walk the case →
AnthropicEnterprise SaaS / Security

RAG agents across tenant boundaries

One retrieval agent answers questions over many customers’ documents, calling search and fetch tools against shared indexes.

walk the case →
AnthropicAI Platform / Security

Untrusted tools from an MCP marketplace

A team lets its agents install and call third-party MCP tools — code shipped by unknown vendors and updated on the vendor’s schedule, not yours.

walk the case →
Google / Linux FoundationAgent Orchestration

Multi-agent systems that call each other

A supervisor agent delegates to specialists that in turn invoke one another’s tools over an agent-to-agent (A2A) protocol. Authority has to survive every hop without inflating.

walk the case →
AWSCloud Platform / IAM

Agents that act on AWS

An agent writes to DynamoDB, drops files in S3, or triggers Lambda — today that usually means a long-lived IAM access key sitting in the agent’s environment.

walk the case →
Okta + EntroSecurity / IAM

Complements your identity & secrets stack

You already run an identity provider and a secrets / non-human-identity platform — they issue the agent’s token and govern which credentials exist. Neither decides whether a given agent action should run, or proves that it did.

walk the case →
AICPACompliance / GRC

Audit evidence for autonomous agents

An auditor asks the question no one has a clean answer to: what governs your autonomous agents, and can you prove what each one did and who authorized it?

walk the case →

Your agent isn’t on this list? The shape is the same.

If an agent can reach a system that can’t tell it no, it belongs behind MCPIP. Bring the highest-consequence action you’re nervous about automating — we’ll walk the gate for it.