Skip to content

Resource

Every MCP tool, what it can do, and who can switch it off.

One inventory for every MCP server, tool and credential. Use the online editor or the downloadable worksheet to compare what a tool is supposed to do with what its implementation can actually reach. The gap between those two is where the review starts.

Inventory fields

What each tool can reach and who owns it.

  • MCP server inventory
  • Tool permission matrix
  • OAuth scope and token notes
  • Read/write/delete/send/execute action table
  • Approval gate and logging checklist

Example entries

Worksheet preview

Have the platform, security and engineering owners fill it in together before anyone reviews tool access.

Tool row

Server: github-mcp. Tool: create_pull_request. Action: write. Credential: user-scoped OAuth. Approval: required before open PR.

  • Owner
  • Environment
  • Data touched
  • Rollback path

High-impact action gate

Any send, delete, deploy, merge, payment, permission, or customer-visible action must have server-side policy and an audit record.

Log review

Record the tool, action, authorization decision, outcome and operation identifier. Retain only the request details needed for review; redact secrets and sensitive content. Name the owner who can disable the integration.

01

Worksheet columns

  • MCP server, client, owner, environment, and data touched
  • Tool name, parameters, destructive potential, and default authorization
  • Credential source, OAuth scope, token lifetime, and user binding
  • Approval gate, log location, rate limit, rollback path, and emergency disablement

Next step

Build the inventory with the tool owners.

Open the online inventory