Create a policy

A new organization starts with an Allow all rule, so every agent can call every tool until you change it. When you finish, a rule of your own decides which agents can use which tools.

Policies control what your agents are allowed to do. Without any rules, all requests are denied by default, so edit or delete Allow all only once your own rules cover what agents need.

Add a ruleCopy Anchor Link

To create a rule of your own:

1. Navigate to Agent Access in the dashboard
2. Click Add Rule
3. Choose the effect: Allow or Deny
4. Set the scope to target specific resources, agents, users, or groups. Leave it empty to match everything
5. Set tool patterns to choose which tools the rule covers: * matches all tools, or use wildcards like send_*. Tools from a multi-upstream resource (like Microsoft 365) are grouped by upstream; check a group's box to add every tool in it
6. Check the name. It fills in from the rule as you build it, so it already describes what the rule does. Replace it with your own name
7. Set the status to Active to start enforcing it. New rules start as Draft, which saves the rule without enforcing it
8. Click Create

As you fill in the scope and tool patterns, the Impact Preview beside the sentence shows how many tools and agents the rule would cover and which existing rules it overlaps. Use it to catch a pattern that matches far more, or far less, than you meant.

A new deny rule goes to the top of the list, so it takes precedence over the default Allow all rule. Every other new rule, such as an allow, goes to the bottom, below rules you already have. The Impact Preview shows where the rule lands. Choose a different position with Place at before you click Create.

How rules workCopy Anchor Link

Rules are evaluated top-to-bottom: the first match wins. If no rule matches, the request is denied.

• Allow rules permit the tool call
• Deny rules block it
• Drag rules in the table to reorder them

Put more specific rules above more general ones. For example, a deny rule for delete_* at position 1 blocks deletes even if an allow-all rule exists below it.

Next stepsCopy Anchor Link

Continue to Connect an agent to point a client at the gateway and put this policy to work.

Once basic access is working, refine it with scope-by-tag, CEL conditions, and argument-level conditions on the live tool-call payload. See the full Policies guide for all of it.