tool-set-enabled-state

Enable or disable MCP tools by name via JSON batch input.

3.8k|349|Updated Apr 2, 2025
One-click install
npx skills add https://github.com/IvanMurzak/Unity-MCP --skill tool-set-enabled-state-ivanmurzak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-set-enabled-state
Source: https://github.com/IvanMurzak/Unity-MCP/tree/main/Unity-MCP-Plugin/.claude/skills/tool-set-enabled-state
Command: npx skills add https://github.com/IvanMurzak/Unity-MCP --skill tool-set-enabled-state-ivanmurzak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable precise control over which MCP tools are available to the AI agent by tool name, ensuring the runtime environment only exposes approved capabilities.

Core Features & Use Cases

  • Enable or disable specific MCP tools by name to tailor agent capabilities for safety, performance, or task-specific workflows.
  • Support batch updates by providing a list of tools with their desired enabled state, including optional logging for audit.
  • Use cases include restricting experimental tools in production, testing tool availability during runs, and preserving reproducible tool configurations.

Quick Start

Use the unity-mcp-cli run-tool tool-set-enabled-state command with a JSON input that lists tool names and their enabled state to toggle the available tools for the AI agent.

Frequently Asked Questions about tool-set-enabled-state

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

FAQPage Schema
How do I enable or disable specific MCP tools for an AI agent?

You can control MCP tool availability by running the unity-mcp-cli command with a JSON input containing a tools array, where each object specifies a tool name and its enabled boolean state.

Can I batch update the enabled state of multiple MCP tools at once?

Yes, you can batch update MCP tools by submitting a JSON input with a tools array where each object includes the tool Name and Enabled fields, toggling multiple tool states simultaneously.

How do I restrict experimental MCP tools in a production runtime environment?

You can restrict experimental MCP tools in production by passing a JSON batch with the tool names and Enabled set to false, ensuring the runtime only exposes approved agent capabilities.

Is it possible to log changes when toggling MCP tool availability?

Yes, include the optional includeLogs flag in the JSON input to generate an audit trail when applying batch updates to toggle the enabled state of MCP tools.

Why does my AI agent still see a disabled MCP tool during the runtime session?

If a disabled MCP tool remains visible, verify the JSON input structure includes the top-level tools array with the exact tool Name and Enabled fields set to false to ensure the runtime environment applies the restrictions.