# MCP Permission Rule

> A rule that covers the tools of one MCP server.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** mcp__server__*, mcp__github__get_*

## Think of it like

It is like a pass for one shop in a mall. Or for one desk in that shop.

## Definition

An MCP permission rule matches the tools an MCP server gives Claude. Write mcp__ then the server name, then two underscores and a star, to cover all its tools. Name one tool in full to cover just that one. A deny rule of mcp__* blocks every MCP tool. An allow rule must name its server, so mcp__* alone allows nothing.

## Example

Lucy lets the GitHub server's read tools run freely. Tools that create issues still ask her first.

## Example code

```json
{
  "permissions": {
    "allow": ["mcp__github__get_*"],
    "ask": ["mcp__github__create_*"]
  }
}
```

Read GitHub freely, ask before creating.

## Why it matters

One server can hold safe tools and risky ones side by side. These rules split them.

## Common mistake

Allowing mcp__* to trust every server. An allow rule with no server name is skipped.

## Three principles

- **mcp__server__*.** All its tools.
- **Full name.** One tool.
- **Allow needs a server.** mcp__* is skipped.

## Related terms

- [MCP Tool](https://learn.benibix.com/term/ai/mcp-tool)
- [MCP Server](https://learn.benibix.com/term/ai/mcp-server)
- [Permission Rule](https://learn.benibix.com/term/ai/permission-rule)

---

Source: https://learn.benibix.com/term/ai/mcp-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.
