MCP can expose useful tools, such as reading a ticket or searching internal documentation. The connection alone does not decide which actions your task authorizes. A server may expose both read and write capabilities, and a read-only request should not silently gain mutation access. In this lesson you select a narrow reading capability, keep writes behind a separate decision and exclude customer records from arguments. The practice session is fully local and makes no MCP call. In real work, review the server, tool description and authentication boundary as dependencies. A tool's reassuring name is not evidence about what data it receives or where it sends it.
A worked artifact for a separate fictional task. Compare its actions with the contract.