execute_claude_code_feature

THE RISK

High Risk

Why execute_claude_code_feature needs a policy

This tool executes arbitrary code within the Obsidian vault environment. While not immediately destructive by design, executing code in headless mode creates significant risk of unintended consequences—file modifications, data corruption, or external API calls—if the AI agent misuses it. The blast radius is substantial because the code runs with the vault's permissions.

From the tool's definition Tool name 'execute_claude_code_feature' and description 'Execute Claude Code in headless mode to implement a feature' indicate execution of code with side effects.

Documented attack patterns abuse exactly the kind of access execute_claude_code_feature gives an agent:

POLICY

How to control execute_claude_code_feature

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_claude_code_feature:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_claude_code_feature": {
      "limits": [
        {
          "counter": "execute_claude_code_feature_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

execute_claude_code_feature stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Obsidian Ai Curator — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian Ai Curator tools

Destructive cleanup_temp_directories Clean up temporary directories created by Claude Code Destructive git_rollback Rollback to a previous git commit Execute execute_claude_code_fix Execute Claude Code in headless mode to fix an issue Write append_to_daily_note Append content to daily note Write init_project Initialize a new project with playbook and optional repository integration Write create_bug_report Create an automated bug report from an error Write create_feature_request Create a feature request with design documentation Write create_github_issue Create a GitHub issue (can trigger Claude Code)

All 27 Obsidian Ai Curator tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Obsidian Ai Curator → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_claude_code_feature

What does the execute_claude_code_feature tool do? +

Execute Claude Code in headless mode to implement a feature. It is categorised as a Execute tool in the Obsidian Ai Curator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_claude_code_feature? +

Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for execute_claude_code_feature: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Obsidian Ai Curator. Nothing to install.

What risk level is execute_claude_code_feature? +

execute_claude_code_feature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_claude_code_feature? +

Yes. Add a rate_limit block to the execute_claude_code_feature rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block execute_claude_code_feature completely? +

Set action: deny in the PolicyLayer policy for execute_claude_code_feature. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides execute_claude_code_feature? +

execute_claude_code_feature is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian Ai Curator tool call.

Start from Obsidian Ai Curator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →