Protocol
Rehearse an AI automation with test data
Start with test data and limited permissions.
Before you use it
- Use when
- An assistant proposes to rename files, process email or edit your calendar through an integration.
Keep this limit in mind
- Passing this rehearsal does not authorise a real run or guarantee its safety. Follow the applicable data-handling rules.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Check which accounts and tools the assistant can access. Use invented records in a separate test folder or workspace, with only the permissions the rehearsal needs. Check that it cannot reach production files, send real messages or spend money. Copying real records does not remove their sensitive content. Enforce the limits through tool or account controls, not just a prompt.
Steps
- Compare planned changes with actual results, including an exception and a request outside the allowed scope.
- If isolation or permissions are unclear, stop at a preview. Before a real run, confirm its permitted targets and actions, including any required approval for high-impact changes.
An example
A renaming test can change only invented files in its test folder. A request to rename another invented file outside it should be refused, even if the model suggests doing so.
Check your result
Expected changes occur only within the test scope, and prohibited actions are refused. A preview alone has not tested execution.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingRehearse an AI automation with test data
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaCompare prompt versions on saved test cases
Evidence and sources
OWASP describes damaging actions from unexpected or manipulated model outputs and recommends limiting tool functions and permissions, approving high-impact actions and enforcing authorisation in downstream systems.
Claim limit: Security-practice guidance, not measured proof that this consumer rehearsal prevents harm. The invented records, isolated test workspace, refused out-of-scope case and preview fallback are editorial adaptations; a successful rehearsal grants no production authority or security certification. Source reading history: selected_passages; 2026-10-11; LLM06:2025: risk examples and mitigation strategies 1-7, especially minimal functionality/permissions, high-impact approval and downstream authorisation. The cited official page was retrieved on 2026-10-10 and the named passages were inspected. Card-specific adaptations are independent editorial reasoning, not validated improvements. On 2026-10-11 these selected passages were read again for card 9798. The rehearsal is an authored workflow; no tool isolation, production deployment, attack-resistance or empirical effectiveness was tested. Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review.
LLM06:2025 Excessive Agency · LLM06:2025 Excessive Agency: Common Examples of Risks; Prevention and Mitigation Strategies 1-7
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-13