# MCP business tool-scope worksheet

AI Systems Studio · 2026-09-13 · Editable planning aid.

## Decision

- Business workflow and owner:
- Clients that need the same tools:
- Existing connector or direct API alternative:
- Reason MCP adds useful reuse:
- Maintenance owner and supported versions:

## One row per tool

| Tool | Caller identity | Read resources | Allowed write | Required approval | Timeout/fallback | Audit fields |
|---|---|---|---|---|---|---|
| Example: account summary | Current signed-in user | Assigned account | None | None for permitted read | Show unavailable state | Actor, account ID, outcome |
| Example: proposed note | Current signed-in user | Assigned account | Exact approved note | Bound to account and content | Keep draft; do not silently retry | Actor, candidate ID, approval ID, outcome |

## Verify before a pilot

- Token audience and user permission checks happen outside the model.
- Tool arguments are validated against a bounded schema.
- Approvals expire or become invalid when the payload changes.
- Revoked users and inaccessible resources are denied.
- Unexpected destinations, deletion, and ownership changes are excluded unless separately authorized.
- Failure and duplicate-write behavior are tested with synthetic inputs.

Guide: https://www.aisystemsstudio.com/blog/model-context-protocol-business-guide