Skip to content
BENIBIX Learn

MCP Permission Rule

AI⌨️ Claude CodeConfiguration

Also known as mcp__server__*, mcp__github__get_*

A rule that covers the tools of one MCP server.

Think of it like

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

Example

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

Why it matters

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

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 code

json
{
  "permissions": {
    "allow": ["mcp__github__get_*"],
    "ask": ["mcp__github__create_*"]
  }
}
Read GitHub freely, ask before creating.

Common mistake

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

Key takeaways

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