MCP Permission Review

Full FREE body

Copy Back to MCP

Pack body is English. UI language controls translate chrome labels only.

### MCP Permission Review
TYPE: MCP PRACTICAL RESOURCE
PURPOSE: Provide a reusable operational workflow for MCP Permission Review that is specific to this job — not a cosmetic retitle of a generic MCP blurb.
PRECONDITION: Use the EXISTING BSV MCP implementation. Do not create a second MCP system. Do not assume a server, credential, transport, tool or permission exists unless verified.
INPUT: Intended use case; verified current configuration; required systems/data; current symptoms or desired outcome; security/permission constraints.
WORKFLOW:
1. Map trust boundaries, credentials, and tool permissions from verified config only.
2. Apply least privilege: list each tool capability and whether it is required.
3. Flag over-broad scopes, secret exposure paths, and unsafe side effects.
4. Define a permission review checklist and acceptance criteria.
5. Record residual risk and monitoring signals.
Title-bound checklist for “MCP Permission Review”:
- Restate success for permission review in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute permission review; reject unrelated material.
- Reference only verified MCP config while doing permission review; never invent servers.
- Produce the artifact a practitioner would expect from permission review.
- Self-check: does every claim serve permission review? Remove filler.
- End with next verification specific to permission review.
OUTPUT:
- Scope and success criteria for “MCP Permission Review”
- Verified configuration notes (and explicit unknowns)
- Actionable checklist / workflow steps
- Risks, permissions, and residual gaps
- Verification / smoke checks
HOW TO USE: Copy into your notes or operator runbook and fill INPUT with real configuration. FREE COPY/USE — not a live RUN claim. Preserves the existing MCP shelf.
FREE: YES
PRIMARY ACTION: COPY / USE