miyabi__handle_development_task

WHAT IT DOES

What miyabi__handle_development_task does on Enhanced Miyabi MCP Server

AI agents invoke miyabi__handle_development_task to trigger actions in Enhanced Miyabi MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why miyabi__handle_development_task needs a policy

The description indicates this tool performs two actions: creating an Issue (Write) and running an Agent (Execute). Per the severity rules, Execute > Write, so the category is Execute. The blast radius is high because an AI agent misusing this tool could trigger arbitrary development agent executions and create unintended issues in a project management system.

From the tool's definition 「Issue作成→Agent実行」 (Issue creation → Agent execution) — the tool both creates issues (Write) and executes an agent, which triggers external operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

miyabi__handle_development_task Rate-limited

miyabi__handle_development_task 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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Enhanced Miyabi MCP Server, so you can run agents against it safely.

FAQ

Questions about miyabi__handle_development_task

What does the miyabi__handle_development_task tool do? +

開発タスクを処理します（Issue作成→Agent実行）. It is categorised as a Execute tool in the Enhanced Miyabi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on miyabi__handle_development_task? +

Register the Enhanced Miyabi MCP Server MCP server in PolicyLayer and add a rule for miyabi__handle_development_task: 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 Enhanced Miyabi MCP Server. Nothing to install.

What risk level is miyabi__handle_development_task? +

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

Can I rate-limit miyabi__handle_development_task? +

Yes. Add a rate_limit block to the miyabi__handle_development_task 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 miyabi__handle_development_task completely? +

Set action: deny in the PolicyLayer policy for miyabi__handle_development_task. 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 miyabi__handle_development_task? +

miyabi__handle_development_task is provided by the Enhanced Miyabi MCP Server MCP server (mo666-med/enhanced-miyabi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.