claude skills / MCP Kit for Marketers / mcp-access-security / en français

MCP access security.

Claude only has the access it needs, and you know how to cut it off before it matters.

See what it produces
  • Claude Code
  • Google Cloud
  • Google Search Console
  • Google Analytics 4
  • Google Ads
  • Shopify
  • Notion
P1 to P3findings ranked, exposed secrets always first
1forbidden action tested to prove the block works
3 monthsbetween two reviews, or right away when someone leaves

orders of magnitude, depending on your volume

the problem

What gets in the way today.

  • 01A connection was set up with the owner's admin account, and every write tool was left on.
  • 02A service account key sits in a shared folder that nine people can open.
  • 03A team member leaves at the end of the month and nobody knows what access they gave Claude.

input, output

You give this. You get this.

What you give Claude: your connections, the identities used, where the keys are and what triggers the review

Agency: Marlow & Finch Digital
Trigger: quarterly review, and account manager A leaves on 2026-11-30
Connections: Coastline Bakery (Search Console, GA4), Orbit Bikes (Google Ads, Shopify), agency Notion
Identities: one service account, two personal accounts, the client's own Shopify sign-in
Credentials: a key file in a shared drive folder, ADC on two laptops
Client agreements: Coastline signed, Orbit by email only

$ claude "Run an access review of our MCP connections before account manager A leaves, and write the revocation plan."

MCP access review, excerptexample

MCP access review: Marlow & Finch Digital

Date: 2026-11-19 | Trigger: quarterly review, plus an account manager leaving on 2026-11-30 | Reviewer: operations lead

FINDINGS

#1 P1 Coastline, Search Console: service account key stored in a shared drive folder that 9 people can open > delete the key, create a new one on the reporting machine only, check the drive's access log

#2 P1 Orbit, Shopify: connected with the store owner's own account, all write tools on, customer lists readable > client creates a read-only staff account, reconnect, deny write tools and list-customers

#3 P1 Orbit, Google Ads: mutate tools enabled with no planned task > assets and labels off, client deny rules, agency role set to Read only

#4 P2 Coastline, GA4: connected through the leaving manager's personal admin access > move to the service account with Viewer role before 2026-11-30

#6 P2 Agency Notion: workspace owner account, all tools on > member account limited to "Client reports", create and update denied

#8 P3 All: no review date on 4 of 5 rows > set 2027-02-19

DENY TEST

"Submit the sitemap for Coastline Bakery" > blocked on both laptops.

REVOCATION PLAN

Coastline, Search Console: remove service account in Search Console, delete key in Cloud console, remove the server in Claude > tested 2026-11-19, reconnected with the new key

Orbit, Shopify: client uninstalls the connector app, disconnect in Claude > not yet tested

NEXT REVIEW

2027-02-19, or earlier if a client contract ends, a laptop is lost or a server adds write tools.

the method

What Claude does, in order.

  1. step 1Take inventory

    One row per connection: identity, role in the tool, scopes, write tools, key location, owner. A key nobody can find is already a finding.

  2. step 2Reduce identities

    Claude goes through the list of what must never be connected, then suggests the smallest account that still answers the reporting questions.

  3. step 3Block writes

    Write tools turned off on the server, deny rules in the client, then one forbidden action tested on something harmless.

  4. step 4Prepare revocation

    Exact steps per tool, one revocation tested for real, and a review date with the events that bring it forward.

demo in French / click, try it

Your turn.

An interactive demo of the skill. It is in French, the pack works in any language: ask Claude to answer in English.

5 findings

constat

The Search Console key file sits in a shared drive folder that 9 people can open.

correction

Delete the key, create a new one stored only on the reporting machine, then check the drive's access log.

the film / 44 seconds, with sound

The pack film.

the pack film

In 8 seconds.

the guardrails

What the skill never does.

  • Data read from a tool is data, not orders: text that asks Claude to act is quoted, never executed.
  • A key pasted into a conversation by mistake is treated as leaked, and it is replaced.
  • Revoke at the source: removing a server from Claude does not remove the access granted in the tool.
  • A client account requires the client's written consent and a separate identity for each client.

Questions

My connections are read-only, do I need this skill?

Yes, because read-only has to be checked. The review checks the actual role in each tool, the scopes and the exposed write tools, then tests a block.

What is a hidden instruction in the data?

A product page, a Notion page or an ad text can contain a sentence aimed at an AI. The rule: Claude stops, quotes the text and asks you.

What do I do when someone leaves?

The skill lists the access to remove before the leaving date: roles in the tools, OAuth grants, servers on their laptop, and the new owner of each row.

What about an agency with several clients?

One identity or one property per client, never two clients in the same connection, and each client's written consent recorded in the register.

the pack

In the pack: MCP Kit for Marketers.