AI agents invoke expert_delegate to trigger actions in Musubix. 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 triggers external AI expert operations, routing tasks to specialized agents. The effects depend on the message content and which expert is selected, making it an Execute-category tool. Severity is high because an AI agent could misuse this to dispatch arbitrary tasks to specialized AI systems, with unpredictable downstream effects depending on what those experts can do.
From the tool's definition "Delegate a task to a specialized AI expert" and "system automatically selects the appropriate expert based on the message content"
Attacks that exploit this kind of access
Delegate a task to a specialized AI expert. The system automatically selects the appropriate expert based on the message content, or you can specify one explicitly. It is categorised as a Execute tool in the Musubix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Musubix MCP server in PolicyLayer and add a rule for expert_delegate: 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 Musubix. Nothing to install.
expert_delegate 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 expert_delegate 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 expert_delegate. 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.
expert_delegate is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). 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 →