Roblox Studio MCP Open Cloud Permission Worksheet - 2026
If you searched roblox mcp permission worksheet after November 4, 2026, you do not need another capability essay. You need a fill-in permissions worksheet that forces an access-level choice, a per-section scope table, upload-folder paths, Skills awareness, collaborator seat initials, an HTTP save check, and a signed PERMS_OK (or HOLD with owner) before the first external MCP client calls open_cloud_invoke on money, publish, or permanent uploads.
Roblox announced Studio MCP Server Updates: Open Cloud Access in Your MCP Client and Asset Import Workflows. Official controls live in Use Open Cloud with the Studio MCP server. The Weekly Recap: November 2–6, 2026 documents the unsaved-place HTTP allow-list caveat.
This URL is the permission evening lab. It is not the what-changed map. It is not the Stop Granting Without Per-Game Permissions refusal. It is not the 12 Free MCP Open Cloud Checks scorecard. Those own explanation, refusal rhetoric, and pass/fail lists. This URL owns the fill-in go/no-go receipt.
Why this matters now
Teams will still “mean to tighten scopes next sprint” while someone flips Full access, wires Cursor, and asks the agent to set up game passes on a live experience. Studio signs the token — the blast radius is whatever you left on. The failure mode is classic: one seat is careful, a contractor inherits folklore, Money stays on overnight, and Monday’s store becomes an agent incident.
Direct answer: Before you call the team “ready for Open Cloud agents,” fill Sections A–J. Green means access level is intentional, high-blast sections are off or time-boxed, upload folders are minimized, seats are initialed, and a Look dry-run passed. Red means HOLD — do not wire write-capable agents. Re-read Creator docs the morning you latch PERMS_OK.
Who fills this worksheet
| Audience | Outcome |
|---|---|
| Beginners | One path: open tab → set Balanced → fill scope table → sign |
| Developers | Seat inventory, upload paths, HTTP save order, revoke plan |
| Creators | Discord paste that stops “Full access for demos” folklore |
| Companies | Diligence receipt — scopes, owners, timestamp, screenshot |
Time: 60–120 minutes for a three-seat team; longer if live monetization is in scope.
Honest limit: DevForum + mcp-open-cloud are authorities. If this page and docs disagree, docs win. Capability depth: what-changed. Refuse codes: Stop. Scorecard: 12 checks.
Non-repetition
| URL | Job |
|---|---|
| MCP Open Cloud what-changed | Capability map |
| Stop Granting Without Permissions | Refuse ladder |
| 12 Free MCP Open Cloud Checks | Pass/fail scorecard |
| DevForum MCP Open Cloud | Primary ship note |
| Creator Hub mcp-open-cloud | Official permissions docs |
| Weekly Recap Nov 2–6 | HTTP allow-list caveat |
| Unreal MCP loopback Stop | Cross-engine refuse |
| Fall roadmap | Broad ladder |
| Roblox Studio guide | Platform hub |
| 25 Discords | Paste channel |
| HTTP 403 help | Proxy while fetching |
| Courses | Learning ladder |
| This URL | Fill-in MCP permission worksheet |
Official facts you must quote (not invent)
From the DevForum announcement and Creator docs:
- External MCP clients can call Open Cloud via
open_cloud_invoke. - Studio manages credentials — no Open Cloud API key required for this path.
- Permissions are per person, per game.
- Access levels: Safe / Balanced / Full access / Custom.
- Full access includes high-risk scopes (Robux, players, live publish).
- Skills:
rbx-open-cloud-usage,rbx-permissions,rbx-import-asset. - These permissions apply to external MCP clients only — not built-in Assistant.
- Uploads are permanent and moderated; you own agent uploads.
- Unsaved places cannot add HTTP allow-list domains until Save/Publish.
Pasteable diligence line:
We ran a Studio MCP Open Cloud permission worksheet: set per-game access level, filled the scope table, minimized upload folders, initialed collaborator seats, dry-ran Look scopes, and signed PERMS_OK (or HOLD with owner) before wiring write-capable agents.
Section A — Session lock (fill in)
| Field | Your answer |
|---|---|
| Operator tonight | ____ |
| Date / local time | ____ |
| Experience name / universe ID | ____ |
| Place is non-prod / live (circle) | non-prod / live |
| Permissions owner (one human) | ____ |
| External MCP client (Cursor / Claude / Codex / other) | ____ |
| Official docs read Y/N | ____ |
| What-changed sibling skimmed Y/N | ____ |
| Stop sibling skimmed Y/N | ____ |
| 12-checks scorecard 1–4 green Y/N | ____ |
A-gate: If permissions owner is “whoever is free,” assign a name. If docs unread, stop and open mcp-open-cloud first. Prefer non-prod for first PERMS_OK.
Beginner first path (twenty minutes)
- Open the experience in Studio.
- Open MCP → MCP Permissions.
- Set Balanced (or Safe).
- Fill Section A + B.
- Do not connect a write agent until B-gate and C-gate are green or HOLD is honest.
Section B — Access level
| Level | Chosen Y/N | Ticket ID if Full / Custom elevate |
|---|---|---|
| Safe | N/A | |
| Balanced | N/A | |
| Full access | ____ (required if Y) | |
| Custom (after tweaks) | ____ |
Screenshot filename / path: ____
B-gate: Full access is N unless ticket ID is filled. Silent Full access → HOLD. See Stop code FULL_ACCESS_REFUSED.
Company note: Attach the screenshot to the diligence zip. “We use Balanced” without a screenshot is folklore.
Section C — Scope table (per section)
Fill On / Off for this seat, this game, tonight. Names follow Creator docs groupings — verify live labels in Studio.
| Section | On/Off | Why on tonight (one line) | Revoke by (time) |
|---|---|---|---|
| Look at your game | |||
| Edit your game | |||
| Players & social | |||
| Save & load data | |||
| Connect to the internet | |||
| Publish & manage assets | |||
| Money & monetization | |||
| Player consequences (if shown) | |||
| Other (name) ____ |
C-gate defaults for first wire:
| Section | First-wire default |
|---|---|
| Look | On (for dry-run) |
| Edit | Off unless named edit task |
| Money | Off |
| Publish & manage assets | Off |
| Save & load data | Off |
| Connect to the internet | Off until place saved + allow-list planned |
| Players / consequences | Off |
C-gate: Money and Publish assets are Off unless Why + Revoke-by are filled. Missing revoke time on an elevated section → HOLD.
Section D — Upload folders
| Folder path approved | Purpose | Still needed after tonight? |
|---|---|---|
| ____ | Y/N | |
| ____ | Y/N | |
| ____ | Y/N |
Home / Documents / Desktop approved as a whole? Y/N (must be N)
D-gate: If Publish & manage assets is On, at least one narrow folder path is listed and home-wide approval is N. If Publish is Off, write “N/A — Publish off.”
Section E — Skills awareness
| Skill | Seen in Skills tab Y/N | Notes |
|---|---|---|
rbx-open-cloud-usage |
||
rbx-permissions |
||
rbx-import-asset |
Team rule written: “Skills ask; humans grant” Y/N: ____
Duplicate Skill customized? Y/N — if Y, note that upstream updates stop: ____
E-gate: At least the three Skills are acknowledged (Seen = Y or “client loads automatically — verified in session”). “Skills mean Full access is fine” → HOLD and reread Stop.
Section F — Collaborator seats
| Seat / human | Access level set by them | Initials | Money Off? | Publish assets Off? |
|---|---|---|---|---|
| Lead | ____ | Y/N | Y/N | |
| Seat 2 | ____ | Y/N | Y/N | |
| Seat 3 | ____ | Y/N | Y/N | |
| Seat 4 | ____ | Y/N | Y/N | |
| Contractor | ____ | Y/N | Y/N |
F-gate: Every human who will use MCP on this game has initials. Blank “inherits lead” rows → HOLD (COLLAB_ASSUMED).
Section G — Assistant vs external MCP latch
Write the latch in your words (one sentence):
Must include: external MCP clients only / Assistant separate.
G-gate: Latch present in runbook or Discord pin. Merged “Assistant uses this tab” folklore → HOLD (ASSISTANT_CONFUSED).
Section H — HTTP / place save order
| Check | Y/N / N/A |
|---|---|
Need HTTP allow-list for execute_luau tonight? |
|
| Place Saved or Published to Roblox before adding domains? | |
| Domains list (comma-separated) | ____ |
| Known caveat read (Weekly Recap) Y/N |
H-gate: If HTTP needed, Save/Publish is Y before domains. Attempting allow-list on unsaved place → HOLD until saved.
Section I — Dry-run + revoke plan
| Step | Done Y/N | Evidence |
|---|---|---|
Look-only open_cloud_invoke / agent read succeeded |
Log snippet / note ____ | |
| No Money/Publish calls in dry-run | ||
| Elevated task (if any) completed | Ticket ____ | |
| Elevated sections revoked same day | Screenshot after ____ | |
| Discord paste sent |
Discord paste template:
MCP permission worksheet filled for [experience]. Access [Safe/Balanced/Custom]. Money/Publish [off / time-boxed until HH:MM]. PERMS_OK / HOLD: [circle]. Owner: [name].
I-gate: Look dry-run Y before any write wire. If elevated task ran, revoke Y same day.
Section J — Sign PERMS_OK or HOLD
| Outcome | Circle one |
|---|---|
| PERMS_OK | All A–I gates green; screenshot attached; owner signed |
| HOLD | Any red gate; write blocker code below |
| Field | Value |
|---|---|
| Outcome | PERMS_OK / HOLD |
| Blocker code (if HOLD) | FULL_ACCESS_REFUSED / MONEY_SCOPE_OPEN / PUBLISH_SCOPE_OPEN / COLLAB_ASSUMED / ASSISTANT_CONFUSED / UPLOAD_FOLDER_WIDE / HTTP_UNSAVED / DRY_RUN_MISSING / OTHER ____ |
| Owner signature (type name) | ____ |
| Timestamp | ____ |
| Screenshot path | ____ |
| Next review date | ____ |
J-gate: PERMS_OK without screenshot → invalid. HOLD without owner → invalid. Paste the diligence line only after a real signature.
Refuse codes (quick reference)
| Code | Meaning |
|---|---|
FULL_ACCESS_REFUSED |
Full access without ticket |
MONEY_SCOPE_OPEN |
Money on without Why + Revoke-by |
PUBLISH_SCOPE_OPEN |
Publish assets / Edit on without task |
COLLAB_ASSUMED |
Seats not initialed |
ASSISTANT_CONFUSED |
Policy merges Assistant + MCP |
UPLOAD_FOLDER_WIDE |
Home-wide upload approval |
HTTP_UNSAVED |
Allow-list before Save/Publish |
DRY_RUN_MISSING |
No Look dry-run |
PERMS_OK |
Worksheet green — wire allowed per plan |
CapEx four-liner (diligence zip cover)
- Scope — Studio MCP Open Cloud permissions worksheet per person, per game.
- Cost — one lab evening vs accidental publish/spend/upload from chat.
- Evidence — filled A–J + Permissions screenshot + Discord paste.
- Owner — named human on Section J.
Worked example — first non-prod PERMS_OK
- Section A: non-prod copy; owner = tech lead.
- Section B: Balanced; screenshot saved.
- Section C: Look On; Money/Publish/Edit Off.
- Section D: N/A — Publish off.
- Section E: three Skills acknowledged.
- Section F: lead + one contractor initialed; both Money Off.
- Section G: latch written.
- Section H: HTTP N/A tonight.
- Section I: Look dry-run pass; Discord paste.
- Section J: PERMS_OK signed.
Worked example — HOLD then fix
- Contractor arrives; lead says “just use Full access.”
- Section B fails →
FULL_ACCESS_REFUSED. - Switch contractor seat to Balanced; Money Off.
- Re-run F initials.
- Look dry-run on non-prod.
- Sign PERMS_OK only after B/C/F green.
Audience ramps
Beginner path
Complete A–B–C with Balanced and Money/Publish Off. Sign HOLD if anything is unclear — HOLD is success when it prevents a live write. Then ask a lead to finish D–J.
Developer path
Automate nothing fancy: keep the scope table in the repo as docs/mcp-perms-[experience].md, update screenshots after every elevate/revoke, and block “agent Open Cloud” PRs without a current PERMS_OK timestamp less than 14 days old (or per your policy).
Creator Monday checklist
- [ ] Worksheet opened for the live experience (not only folklore).
- [ ] Balanced or Safe recorded.
- [ ] Scope table filled.
- [ ] Seats initialed.
- [ ] Discord paste sent.
- [ ] PERMS_OK or honest HOLD.
Scheduling table
| When | Action |
|---|---|
| Before first MCP Open Cloud wire | Full A–J |
| Before any Money/Publish elevate | Update C + D + I revoke time |
| Weekly | Spot-check B screenshot still matches Studio |
| Partner ask | CapEx + Section J |
Failure modes this worksheet catches
| Failure | Missed section | What you say instead of folklore |
|---|---|---|
| Silent Full access | B | HOLD + FULL_ACCESS_REFUSED |
| Money left on overnight | C + I | Revoke; update revoke-by next time |
| Contractor “uses lead setup” | F | Each seat initials scopes |
| Home folder approved | D | Narrow export path only |
| HTTP rage on unsaved place | H | Save/Publish first |
| “Assistant is locked” | G | Rewrite latch |
| Wire without dry-run | I | Look-only first |
| Diligence with no artifact | J | Screenshot + signature |
If Discord argues “the model hallucinated a game pass,” open Section C first. Most “hallucinations” are enabled scopes doing what you allowed.
Ninety-minute evening timeline
| Minute | Section | Outcome |
|---|---|---|
| 0–10 | A | Owner named; non-prod preferred |
| 10–20 | B | Balanced + screenshot |
| 20–35 | C | Scope table; Money/Publish Off |
| 35–45 | D–E | Folders N/A or narrow; Skills noted |
| 45–60 | F–G | Seats initialed; Assistant latch |
| 60–70 | H | HTTP N/A or saved place |
| 70–85 | I | Look dry-run + Discord paste |
| 85–90 | J | PERMS_OK or honest HOLD |
Do not skip to J because “we already read the blog.” The receipt is the product. If you only have forty minutes, finish A–C and sign HOLD — a partial green sheet with an honest red gate beats a fake PERMS_OK.
Company diligence — questions this receipt answers
| Partner question | Worksheet answer location |
|---|---|
| Who owns agent Open Cloud risk? | A + J owner |
| What is default access on this experience? | B screenshot |
| Can agents spend or publish tonight? | C Money / Edit rows |
| Which folders can agents upload from? | D |
| Do contractors share the lead’s token? | F (no — per person) |
| Is Assistant covered by this tab? | G (no) |
| When was this last reviewed? | J next review date |
Attach A–J export (markdown or PDF) plus the Permissions screenshot. That package beats a slide that says “we take AI safety seriously.”
How this pairs with siblings
| Topic | Job |
|---|---|
| What-changed | Map |
| Stop | Refuse |
| 12 checks | Scorecard |
| This URL | Fill-in receipt |
Do not paste the essay as proof. Paste Section J + screenshot.
Internal links
Map: MCP what-changed. Stop: Stop Granting Without Permissions. Checks: 12 Free MCP Checks. Hub: Roblox Studio guide. Roadmap: Fall lock. Cross-engine: Unreal MCP Stop. Help: HTTP 403. Resources: 25 Discords. Courses: /courses.
Key takeaways
- This worksheet is the fill-in go/no-go before Open Cloud agents.
- Sections A–J must be filled — not skimmed.
- Full access needs a ticket or HOLD.
- Scope table defaults Money/Publish Off.
- Upload folders must be narrow when Publish is On.
- Skills teach; humans grant.
- Collaborators set and initial their own scopes.
- Assistant ≠ external MCP latch required.
- Save/Publish before HTTP allow-list.
- Look dry-run before write wire.
- Revoke elevated sections same day.
- PERMS_OK requires screenshot + owner.
- HOLD with owner is a valid outcome.
- CapEx four-liner belongs in diligence zips.
- Quotable: fill the MCP permission worksheet before the first Open Cloud agent session.
FAQ
What is a roblox mcp permission worksheet?
A fill-in lab that records access level, scopes, folders, seats, and signs PERMS_OK or HOLD before wiring agents.
Is this the same as the 12 checks listicle?
No. 12 checks is pass/fail. This page is the receipt you fill.
Official docs?
Use Open Cloud with the Studio MCP server
Can I PERMS_OK on Full access?
Only with a filled ticket in Section B and an honest revoke plan. Prefer Balanced + temporary sections.
Do collaborators share my PERMS_OK?
No. Each seat fills scopes; Section F requires initials.
What if I only use Studio Assistant?
These MCP Permissions apply to external clients. Still write the Section G latch so the team does not confuse surfaces.
Where is the Stop article?
Stop Granting Roblox MCP Open Cloud Without Per-Game Permissions - 2026
How long does PERMS_OK last?
Policy choice — this worksheet suggests a next review date in Section J (commonly ≤14 days or after any elevate).
Sources
- Studio MCP Server Updates: Open Cloud Access… (DevForum)
- Use Open Cloud with the Studio MCP server (Creator Hub)
- Weekly Recap: November 2–6, 2026 (DevForum)