claude-sdk-permissions

Configure tool execution permissions and security policies in the Claude Agent SDK.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Folken2/nuvel --skill claude-sdk-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-sdk-permissions
Source: https://github.com/Folken2/nuvel/tree/main/nuvel/backends/claude_agent_sdk/skills/claude-sdk-permissions
Command: npx skills add https://github.com/Folken2/nuvel --skill claude-sdk-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the friction between agent autonomy and system security by providing a structured framework for managing tool access, preventing unauthorized command execution, and ensuring safe unattended deployments.

Core Features & Use Cases

  • Permission Modeling: Configure granular control using allowlists, blocklists, and six distinct permission modes.
  • Dynamic Gating: Implement custom logic via the can_use_tool callback to validate inputs or rate-limit specific operations.
  • Production Hardening: Safely transition from interactive development to unattended server deployments by enforcing strict tool execution policies.

Quick Start

Configure the agent to use the dontAsk permission mode while explicitly allowing only the necessary filesystem and user lookup tools.

Frequently Asked Questions about claude-sdk-permissions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Claude Agent SDK permissions for unattended server deployments?

To manage Claude Agent SDK permissions for unattended deployments, enforce strict tool execution policies by configuring the dontAsk permission mode. This allows production hardening by explicitly allowing only necessary filesystem and user lookup tools without requiring interactive approval.

What is dynamic gating in Claude Agent SDK security?

Dynamic gating in Claude Agent SDK security is a mechanism to implement custom validation logic via the can_use_tool callback. It allows developers to validate inputs or rate-limit specific operations dynamically per-call, preventing unauthorized command execution by the agent.

How do I configure allowlists and blocklists for Claude agent tool access?

You configure allowlists and blocklists for Claude agent tool access through granular permission modeling. This provides fine-grained control over tool availability by statically defining which tools the agent is permitted to use or blocked from accessing during execution.

What are the available permission modes in the Claude Agent SDK?

The Claude Agent SDK features six distinct permission modes for configuring agent security. These modes allow developers to select the appropriate level of autonomy versus system security when modeling tool access and execution safety policies.

Can I rate-limit specific tool operations executed by a Claude agent?

Yes, you can rate-limit specific tool operations executed by a Claude agent. By implementing custom logic within the dynamic gating can_use_tool callback, you can validate inputs and apply rate-limiting rules to specific operations on a per-call basis.

When do I need to enforce strict tool execution policies for Claude agents?

You need to enforce strict tool execution policies for Claude agents when transitioning from interactive development to unattended server deployments. This production hardening step prevents unauthorized command execution and ensures safe, autonomous operation without human oversight.