plugin_build
Build a plugin from a service key or custom spec. If building from catalog, returns the plugin
This record as markdown: /tools/io-github-0nork-0nmcp/plugin-build.md
What plugin_build does on 0nmcp
AI agents invoke plugin_build to trigger actions in 0nmcp. 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.
Why plugin_build is rated High
This tool triggers code generation and plugin instantiation—operations that execute external logic. While not destructive, the act of building plugins with custom specifications can have side effects dependent on what spec is provided (could invoke third-party code, modify local state, or register handlers). It does not merely read or reversibly write data; it constructs executable artifacts.
From the tool's definition Tool name 'plugin_build' and description 'Build a plugin from a service key or custom spec' indicates it constructs and instantiates plugin code.
Attacks that exploit this kind of access
The rule that runs plugin_build 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 plugin_build, this is the rule to start with:
plugin_build stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 plugin_build call is checked against it from then on.
Questions about plugin_build
Build a plugin from a service key or custom spec. If building from catalog, returns the plugin. It is categorised as a Execute tool in the 0nmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 0n MCP server in PolicyLayer and add a rule for plugin_build: 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.
plugin_build 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 plugin_build 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 plugin_build. 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.
plugin_build 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