Plan the per-holder dispatch for a list of per-token top-k routings.
AI agents use moe_plan_dispatch to create or update resources in Tenzro Ledger MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
This tool appears to create or modify dispatch plans for token routing across multiple holders. While the exact semantics are unclear without implementation details, 'planning dispatch' in a ledger/financial context implies writing configuration or state that directs how tokens or payments flow.
From the tool's definition Tool name 'moe_plan_dispatch' and description 'Plan the per-holder dispatch for a list of per-token top-k routings' indicates creation or modification of dispatch plans.
Attacks that exploit this kind of access
Plan the per-holder dispatch for a list of per-token top-k routings. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for moe_plan_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 Tenzro Ledger MCP. Nothing to install.
moe_plan_dispatch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the moe_plan_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 moe_plan_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.
moe_plan_dispatch is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/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 →