MCP & AI-Agent Security Audit

Your AI agents are touching production. Do you know what they actually do?

Your teams have wired AI assistants into internal systems through MCP servers, one repo at a time, without anyone signing off. This fixed-fee, two-week audit maps the MCP servers and agent integrations we find across your repos, CI, and agreed dev environments, shows what each can reach, and where the exposure is. Run by a Site Reliability Engineer who operates this stack in production.

Book a free 20-min scoping call Read a sample report → See the 4 questions →

✓ Read-only access ✓ Delivered in 2 weeks ✓ ~2 hours of your team's time

Who this is for: engineering and security leads at companies where developers have wired AI assistants (Claude, Cursor, Copilot) into internal tooling and nobody owns the full picture yet. Who it's not for: if your entire agent surface is one local toy server on one laptop, you don't need this yet — bookmark it for when that changes.

// the four questions most teams can't answer

Shadow IT with root access and no logs

MCP servers start as someone's local convenience and drift into production reach. Run these checks against your own org. Each "UNKNOWN" is the gap this audit closes.

agent-surface-scan · production

Inventory How many MCP servers exist in our org, and who owns each one?

UNKNOWN

Blast radius What can each server read, write, or delete? Which ones can reach production?

UNKNOWN

Identity Are agents authenticating with static secrets that never rotate?

UNKNOWN

Audit trail If an agent caused an incident yesterday, could we reconstruct what it did in five minutes?

UNKNOWN

If any line reads UNKNOWN, you're operating an unmonitored attack surface that can act on your systems. You'll find out what it did only after it matters.

// what you get

A fixed-scope engagement with six deliverables and no open-ended billing

Complete agent inventory

Every MCP server and agent integration, with its owner, transport, and exposure level, mapped against your network segmentation.

Blast-radius map

Per-server capability matrix: which tools it exposes, what credentials it holds, and what downstream systems it can act on.

Security findings report

Graded against the OWASP Top 10 for LLM Applications, plus MCP-specific checks: static secrets, missing auth, tool poisoning, exposure.

Observability gap assessment

Which agent actions are invisible to your monitoring today, plus a vendor-neutral plan (OTel, Prometheus) to close the gap.

Prioritized remediation roadmap

Ranked by risk × effort, with week-one quick wins flagged and every item assigned an owner.

Executive readout

A 30-minute walkthrough for engineering and security leadership, with plain findings and clear next steps.

// engagement

Built to run quietly alongside your team

DURATION2 weeks, mostly asynchronous

YOUR_TIME~2 hours: kickoff, access, readout

ACCESSRead-only. Production is never modified.

OUTPUTReport + capability map + 30-min readout

FOLLOW_ONOptional remediation sprint or monitoring retainer

After the audit, teams that keep expanding MCP/agent usage can retain me monthly to review new servers, update monitoring, and keep the agent surface auditable instead of letting it drift back into shadow IT.

Founding-client rate · 3 of 3 slots open

$4,500 fixed

First three clients only, in exchange for a case study you approve and redact before publication. One price covers all six deliverables, with no hourly billing.

Claim a founding slot

// why me

Abu Dzar is a Site Reliability Engineer with deep DevSecOps experience across AWS, Kubernetes, and Terraform. I build and operate MCP servers and agentic pipelines myself, including mcpobserve, an open-source observability proxy for MCP servers. The audit method comes from running this stack in production, which is why the findings are specific actions your team can take rather than a generic checklist.

mcpobserve on GitHub Writeup: the MCP observability gap LinkedIn

// before you ask

The questions every security buyer asks

What access do you actually need?

Read-only, and less than you'd expect: repository access (or just the repos likely to contain MCP configs), your MCP client configurations, and a look at your existing monitoring. I install nothing in your environment and write nothing to production. You can revoke everything the day the readout ends.

Will you sign our NDA?

Yes, yours or mine, before kickoff. All findings are confidential by default. The founding-rate case study is written only with your approval, anonymized and redacted by you before anything is published.

What if you find nothing serious?

Then you get documented evidence that your agent surface is clean: a complete inventory, a capability map, and an observability assessment you can hand to auditors and leadership. Most teams can't produce that evidence today, and a clean result still carries all six deliverables.

What will you NOT do?

No penetration testing, no exploit chains, no social engineering, and no changes to production — ever. I also won't scan your endpoint fleet: discovery covers the repos, CI, and dev environments we agree on at kickoff, not employee laptops via MDM. If you need a pentest of a specific MCP server after the audit, I'll scope that separately or refer you out.

What does the report actually look like?

Exactly like the redacted sample report — a fictional company, but the real structure: full inventory, blast-radius matrix, graded findings against the OWASP LLM Top 10, observability gap assessment, and a sequenced remediation roadmap.

Is this remote? What's the actual time cost for us?

Fully remote and mostly asynchronous. Your team's involvement is roughly two hours total: a kickoff call, granting access, and the 30-minute executive readout. Everything in between happens over email or your ticketing system, on my side of the fence.

Your AI agents are touching production. Do you know what they actually do?

Shadow IT with root access and no logs

A fixed-scope engagement with six deliverables and no open-ended billing

Complete agent inventory

Blast-radius map

Security findings report

Observability gap assessment

Prioritized remediation roadmap

Executive readout

Built to run quietly alongside your team

The questions every security buyer asks

Find out what's already running