Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 1 min read

AI Agent Permissions: Decide What Can Run Without Approval

An AI workflow does not need unrestricted access to be useful. The hard part is deciding which actions are safe to automate, which need a human check, and how to limit the damage if a tool call goes wrong. Clas

An AI workflow does not need unrestricted access to be useful. The hard part is deciding which actions are safe to automate, which need a human check, and how to limit the damage if a tool call goes wrong.

Classify actions by impact

Read-only search is usually lower risk than sending a message, changing a record, issuing a refund, or modifying production infrastructure. Classify each tool by the data it can access, whether it creates an external side effect, and how difficult that side effect is to reverse.

Apply the least privilege

Give the workflow a dedicated identity with only the permissions it needs. Separate read and write tools where possible. Limit scope by resource, action, and time. Use short-lived credentials and keep secrets outside prompts and logs.

Set approval boundaries

Let low-impact, reversible steps run automatically when they can be monitored. Require confirmation for consequential, external, or hard-to-reverse actions. The approval request should show the intended action, target, and relevant contextβ€”not just ask β€œProceed?”

Add limits such as maximum amount, record count, allowed recipients, or deployment environments. Make denials and timeouts fail closed. Log the approval and final result so operators can audit what happened.

Review permissions as the workflow changes. A tool that was harmless in a prototype may become consequential when connected to real customer data or production systems.

More practical AI delivery notes: https://umer-amin.vercel.app/. What action in your workflow should always require a human approval?

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.