factory_spawn
Spawn a new sub-app at https://www.0ncore.com/apps/<slug> by composing one or more capabilities from the brain registry. Capabilities (pick from): notes, service_packager, course_builder, hipaa_scanner, cro9_engine, brand_builder, voice_ai, email_paste, 0nexec, report_builder. Modes: composer — i...
This record as markdown: /tools/io-github-0nork-0nmcp/factory-spawn.md
What factory_spawn does on 0nmcp
AI agents use factory_spawn to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why factory_spawn is rated Medium
An AI agent can call factory_spawn faster than any human can review: one bad instruction and it creates or modifies resources in 0nmcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs factory_spawn safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For factory_spawn, this is the rule to start with:
factory_spawn 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every factory_spawn call is checked against it from then on.
Questions about factory_spawn
Spawn a new sub-app at https://www.0ncore.com/apps/<slug> by composing one or more capabilities from the brain registry. Capabilities (pick from): notes, service_packager, course_builder, hipaa_scanner, cro9_engine, brand_builder, voice_ai, email_paste, 0nexec, report_builder. Modes: composer — independent dashboards on a single page (default) chain — workflow with output flowing top-to-bottom The slug is auto-generated from the name; uniqueness is enforced with a numeric suffix on collision. Owner is set to the calling user (defaults to mike@rocketopp.com when called from the MCP). Returns the new app. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for factory_spawn: 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 0nmcp. Nothing to install.
factory_spawn 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 factory_spawn 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 factory_spawn. 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.
factory_spawn is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue