Hash-aware sibling of build_workflow_links (ChainGraph Standard v0.1 §8.1). Returns an ordered, executable DAG over the ChainGraph suite's verifiable tools, with explicit parent_hash wiring: which upstream execution_hash each step must cite in its chain block. Pass target_tool_id to build the cha...
AI agents invoke build_chaingraph to trigger actions in Ainumbers Mcp Apps. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool_ids | array | — | Explicit ordered list of ChainGraph node tool_ids to wire. |
target_tool_id | string | — | A ChainGraph node tool_id (e.g. "art-15-agent-commerce-conformance"). Builds the chain that produces it. |
Parameters from the server's own tool schema.
This tool constructs and orchestrates an executable directed acyclic graph (DAG) of tool executions, chaining outputs and execution hashes between steps. It triggers and sequences external operations, placing it firmly in Execute.
From the tool's definition Returns an ordered, executable DAG... with explicit parent_hash wiring... Agent loop: run a node, capture its execution_hash, pass it as the parent_hash for each downstream node
Attacks that exploit this kind of access
Hash-aware sibling of build_workflow_links (ChainGraph Standard v0.1 §8.1). Returns an ordered, executable DAG over the ChainGraph suite's verifiable tools, with explicit parent_hash wiring: which upstream execution_hash each step must cite in its chain block. Pass target_tool_id to build the chain that produces that node (walks consumes-edges back to roots), or tool_ids for an explicit ordered list, or neither to list available ChainGraph nodes. Agent loop: run a node, capture its execution_hash, pass it as the parent_hash for each downstream node, then verify with verify_execution_hash. It is categorised as a Execute tool in the Ainumbers Mcp Apps MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_chaingraph accepts 2 parameters: tool_ids, target_tool_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for build_chaingraph: 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 Ainumbers Mcp Apps. Nothing to install.
build_chaingraph 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 build_chaingraph 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 build_chaingraph. 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.
build_chaingraph is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). 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 →