r/devsecops • • 11d ago

MCP access control for coding agents: what does the Claude Code allowlist leave you to handle?

We rolled Claude Code out to about 40 engineers last month and I own the security side of it. Managed settings let us pin which MCP servers are allowed, which covers the obvious stuff. What the allowlist doesn't give me is different tool scopes per team, a log of the arguments that went into each tool call, or anything stopping a secret from riding along in a prompt. Managed hooks could log and block on each laptop, but then I'm writing and running the checks and the log collection myself. Where are you handling MCP access control past the allowlist?

7 Upvotes

9 comments sorted by

3

u/AgileCranberry8785 11d ago

I think a whitelist is only a starting point, especially when several teams are involved. Different teams should have access to only the tools they actually need. Logging tool activity and checking for sensitive information before it gets sent are just as important.

1

u/ParnelliSelfa 10d ago

A gateway in front of the remote MCP servers is a lot easier to run than hooks on 40 laptops. Each call goes through it, it checks the team on the token against tool list and logs the arguments in one place. also helps to know what teams already have wired up before you write the scopes.

The ai inventory picks up mcp configs committed in repos which gives you a decent starting list. Secrets in prompts are a tricky one tho, UserPromptSubmit hook catches obvious key patterns, not much else

1

u/Hot_8500 10d ago

40 engineers on claude code means at least 3 people already asked why their mcp server was blocked, guaranteed

1

u/theJacofalltrades 7d ago

Logging the arguments is the piece I'd push on first, since it's the 1st thing you'll be asked for after an incident. NeuralTrust's agent gateway and Arcade.dev both sit between the agent and the tools as a single control point, so every tool call is on record in one place and not across 40 laptops.

1

u/psycrave 5d ago

The solution you are looking for is called an MCP gateway.