Scaffold a template-based dApp monorepo with starter components: Stylus contract, backend, frontend, indexer, and oracle. Creates a project structure with generic templates to customize.
AI agents use orchestrate_dapp to create or update resources in ARBuilder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ARBuilder environment.
This tool creates new files, directories, and project scaffolding structures in the filesystem. While reversible (the generated files can be deleted), it modifies the filesystem by writing template content. It does not execute arbitrary code, delete data irreversibly, or move money, so Execute, Destructive, and Financial are inappropriate.
From the tool's definition Tool description states it 'Scaffold a template-based dApp monorepo' and 'Creates a project structure with generic templates', which are creation operations that generate new files and directory structures.
Documented attack patterns abuse exactly the kind of access orchestrate_dapp gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ARBuilder, and nothing reaches the server without passing your rules. This is the rule we recommend for orchestrate_dapp:
{
"version": "1",
"default": "deny",
"tools": {
"orchestrate_dapp": {
"limits": [
{
"counter": "orchestrate_dapp_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} orchestrate_dapp stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scaffold a template-based dApp monorepo with starter components: Stylus contract, backend, frontend, indexer, and oracle. Creates a project structure with generic templates to customize. It is categorised as a Write tool in the ARBuilder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ARBuilder MCP server in PolicyLayer and add a rule for orchestrate_dapp: 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 ARBuilder. Nothing to install.
orchestrate_dapp 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 orchestrate_dapp 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 orchestrate_dapp. 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.
orchestrate_dapp is provided by the ARBuilder MCP server (quantum3-labs/arbuilder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ARBuilder, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 ARBuilder tools catalogued and risk-classified — across an index of 43,000+ MCP servers.