# The Blind Spot

## Three problems your current stack can't see

### 1. Shadow MCP

Engineers spun up MCP servers for GitHub, Postgres, internal APIs. Connected to Cursor and Claude Code. Running in production. Your SIEM sees nothing.

### 2. PII leaking through MCP

An agent queries your customer database through MCP. Names, emails, SSNs flow to Claude's API as context. No redaction. Your DLP wasn't built for MCP traffic.

### 3. Prompt injection via MCP

A compromised MCP server injects hidden instructions into tool responses. Your agent follows them. The agent looks normal. The MCP server is the attack vector.

MCP and integrations connect to your data. No LLM control. No visibility. Blind stack.

# How Golf Solves It

## Discover. Enforce. Audit.

Works with Cursor, Claude Code, Copilot, ChatGPT - without controlling the AI, routing the traffic, or changing anyone's workflow.

### 1. Discover

Every MCP server in your environment. Auto-discovered, auto-classified. Which teams, which agents, what data. Including servers you didn't know existed.

### 2. Enforce

Policies per server, agent, team, data type. PII redaction. Prompt injection detection. Sub-millisecond enforcement. Developers never feel it.

### 3. Audit

Works with Cursor, Claude Code, Copilot, ChatGPT - without controlling the AI, routing the traffic, or changing anyone's workflow.

## Deployment

### 3 steps. Live in days.

#### Step 1: Connect

Your identity provider and your SIEM. Golf maps your org and starts streaming logs.

#### Step 2: Deploy

MCP Control Plane in your environment. On-prem, hybrid, or cloud. Data never leaves.

#### Step 3: See everything

Every MCP server. Every agent. Every connection. Secured.

# Why Golf

## Govern MCP without slowing down your engineers

### Zero developer friction

Previous solutions: 17 onboarding steps per developer.

Golf: 3 steps. Engineers keep every tool. Security gets full control.

### Third-party AI tools included

You can't route Cursor, Copilot, or Claude Code through a gateway. They make their own LLM calls. Golf governs at the MCP layer - no integration needed.

### Not LLM guardrails

Guardrails protect what an LLM says. Golf governs what an agent does. When a coding agent reads your codebase through MCP, that's not a content problem.

# Arm Your Champion

## Need to sell this internally?

You can't buy this alone. Here's ammo for the 3–12 people to convince.

- **Executive Summary**  
One-pager for your CISO. Problem, solution, outcomes.  
[Download PDF](https://cdn.prod.website-files.com/69a5e500683f29cfbea15040/69a5e520d288c4961cc2a6a7_pdf-sample_0.pdf)

- **ROI Framework**  
Cost of compliance finding vs. cost of Golf deployment.  
[Download Spreadsheet](https://cdn.prod.website-files.com/69a5e500683f29cfbea15040/69a5e574ab29fa52a7f53e3a_Call-Center-Sentiment-Sample-Data.xlsx)

- **SOC 2 / HIPAA**  
32 slides. The problem, why Golf, what it costs.  
[Download PDF](https://cdn.prod.website-files.com/69a5e500683f29cfbea15040/69a5e520d288c4961cc2a6a7_pdf-sample_0.pdf)