Allowing AI to read lesson preparation materials does not mean it simultaneously has permission to modify the originals or send them to others. Each operation requires a corresponding scope.
Task Instructions and Permissions Are Different
"Don't modify" in a prompt is a behavioral instruction; achieving actual read-only access requires tools, services, or environmental restrictions on modification operations. Requesting "please modify" cannot override an environment that lacks write capabilities.
Check by Operation Target
Which material is being read? Which file will modifications affect? Are the sending target and content already determined? These questions directly determine the scope of the current task.
The MCP examples on this site only provide fixed material queries and do not accept arbitrary file paths. They limit exposed operations but do not claim that the entire running process has system-level read-only isolation.
Compare with a Lesson Preparation Request
"Read specified textbook excerpts and organize them into a lesson plan" requires reading materials and generating content. "Directly overwrite the original lesson plan" additionally involves writing to the original file. "Send the results to all parents" further involves an external target and final content. The latter two items are not automatically granted reasonable scope just because the first request was made.
If the tool being used only provides queries, writing "please modify" will not give it write functionality. When modification is needed, first confirm the specific capabilities and allowed scope provided by the application, then verify the actual results.
Results Still Need to Be Examined After Execution
Permission being granted does not mean the operation succeeded. After success, you should also confirm that the target and content are correct, and preserve verifiable outputs or change records when necessary. Authorization entry points for specific products should follow their documentation, not treating "already connected" as a complete description of permission scope.
Related Concepts in This Section
- Permission: The range of accessible resources and executable operations controlled by applications, services, and execution environments.
For general definitions and technical sources, see the related concepts page, verification date: 2026-09-09. The cases in this section are written for teaching purposes; optional checks serve comprehension and do not restrict continued reading.