Choose the scope of an agent allowance
Decide which actions and resources should share a limit, and test environment, action-name and resource-prefix boundaries.
A shared allowance is useful only if it covers the operations you intended to group. A refund limit for one environment does not become an organization-wide financial cap, and a limit scoped to one action does not automatically cover a second action with a different name.
Anlyon limit scope uses server-controlled values: environment, dimension and unit, optional action name, optional resource prefix, and period. Sessions and agent keys do not define independent copies of the same applicable allowance.
Start with the business boundary
Write down a sentence such as: "All governed USD refunds in the production environment share this daily allowance." Then identify the actual actions that produce those refunds. Check that each has an adapter or an impact declaration that supplies the required quantity.
| Desired boundary | Configuration to examine |
|---|---|
| All USD refunds in one environment | Money dimension, currency, environment and applicable actions |
| Changes to a repository family | Resource-mutation dimension and resource prefix |
| One particular send action | Action-name restriction and declared email quantity |
| A finite migration allowance | Total period and narrowly selected resources |
Inspect the resource identifiers the adapter actually emits before choosing a prefix. A prefix inferred from a display label can miss the real resource.
Test both sides of the boundary
Use two agent credentials inside the same environment and confirm their usage reaches the same applicable limit. Exercise an intended matching action and a deliberately nonmatching action in a safe environment. The second test documents the boundary; it is not a production bypass experiment.
Also test the configured period. A day is a UTC day. If your business closes at a local midnight, document the difference instead of assuming the two windows align.
Keep alternate access visible
Provider requests made outside Anlyon are outside its execution limit. Separate environments also have separate allowances. Remove unnecessary alternate provider credentials or constrain those paths independently. Treat permission to change a limit as an administrative capability.
Use the exact configuration fields and tool permissions. If the quantity itself is unclear, continue with declaring what an action counts.