# Parameter Permission Rule

> A deny or ask rule that checks one value a tool gets.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** Agent(model:opus), Tool(param:value)

## Think of it like

It is like a rule that says no hats. It is about what you wear, not who you are.

## Definition

A parameter permission rule matches one value a tool is called with. It is written as the tool, then a name and a value, such as Agent(model:opus). It works for deny and ask rules on built-in tools. A star in the value matches anything. It cannot match a tool's main field, such as the command in Bash.

## Example

Jack's helpers run on a cheap model. An ask rule on the big model makes Claude check with him first.

## Example code

```json
{
  "permissions": {
    "ask": ["Agent(model:opus)", "Agent(isolation:worktree)"]
  }
}
```

Ask before a costly or isolated subagent.

## Why it matters

Some risk sits in how a tool is called, not which tool. This rule can see that.

## Common mistake

Writing an allow rule this way. Only deny and ask rules match by setting.

## Three principles

- **Tool(name:value).** One setting.
- **Deny and ask only.** Not allow.
- **Not the main field.** Use the normal form.

## Related terms

- [Agent Permission Rule](https://learn.benibix.com/term/ai/agent-permission-rule)
- [Bash Permission Rule](https://learn.benibix.com/term/ai/bash-permission-rule)
- [Permission Rule](https://learn.benibix.com/term/ai/permission-rule)

---

Source: https://learn.benibix.com/term/ai/parameter-permission-rule
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
