Reads and writes
Analysis and editing need different folder permissions.
Guides · MCPENROUZ
AI access permissions: folders, writes and terminal
Local settings define maximum device capabilities. The workspace restricts a client within the permissions you select.
Free2 devices · 100 tool calls per hour
Example task
Documents: reads only, no shell. Development: project reads and writes, shell if tests require it.
Your device · your permissions
Separate capabilities
Deletion, shell and OS processes need separate grants.
Local ceiling
Choose which modes the workspace may enable.
Get started
Choose a directory
Start with one read-only folder.
Review capabilities
Enable writes, deletion and commands for the task.
Save and verify
Confirm local changes and check application permissions.
Example task
A prompt for your AI
Documents: reads only, no shell. Development: project reads and writes, shell if tests require it.
Permissions
File-tool roots are not a shell sandbox. Commands have OS user permissions. Use a separate user, container or VM for isolation.
Details
Deletion and editing
A writable folder permits creation and edits. Deletion needs an additional permission. Removing a folder from the list removes access, not the files.
OS processes
Listing and terminating processes are separate choices. Document reads do not need them. The workspace cannot exceed the local ceiling.
Frequently asked questions
Must I enable everything?
No. Start with reads and add permissions for the task.
How do I remove a folder?
Remove it from the local list and save.
Can the workspace expand access?
Only within local capabilities and the control ceiling.
Next steps
MCPENROUZ · FREE
Connect a device. Start with reads.
Choose a working folder and AI client. Add writes and terminal access as your task requires.