タスクを自動的に適切なハンドラーに振り分けます(開発タスク→Miyabi、一般タスク→Manus)
AI agents invoke miyabi__auto_dispatch 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.
This tool automatically classifies and routes tasks to other handlers/agents, which themselves execute operations (development tasks, article generation). The act of dispatching triggers external operations whose effects depend on the input, making it Execute.
From the tool's definition 「タスクを自動的に適切なハンドラーに振り分けます」(Automatically dispatches tasks to appropriate handlers) — triggers execution of downstream handlers including development task processing via Miyabi Agent and article generation
Attacks that exploit this kind of access
タスクを自動的に適切なハンドラーに振り分けます(開発タスク→Miyabi、一般タスク→Manus). 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.
Register the Enhanced Miyabi MCP Server MCP server in PolicyLayer and add a rule for miyabi__auto_dispatch: 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.
miyabi__auto_dispatch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the miyabi__auto_dispatch 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.
Set action: deny in the PolicyLayer policy for miyabi__auto_dispatch. 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.
miyabi__auto_dispatch 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →