Technical Topic
MCP Boundary Evidence
A practical page for MCP-style tool boundary evidence: side effects, schema, approval, identity, audit, fallback, and review posture.
What this page is for
This page explains how agentic repositories can make tool boundaries visible to reviewers. The goal is not to claim compliance. The goal is to make action risk, approval rules, identity handling, and audit evidence easy to inspect.
Evidence fields
- What can the tool read or write?
- Which side effects require human approval?
- Which identity is used for each action?
- Where is the audit event recorded?
- What is the fallback when the provider is unavailable?