plugin_create
Generate a new custom plugin spec for a service not in the catalog. Auto-infers capabilities from endpoints and maps .0n canonical fields. Saves to ~/.0n/plugins/ for automatic loading. Example: plugin_create({ key:
This record as markdown: /tools/io-github-0nork-0nmcp/plugin-create.md
What plugin_create does on 0nmcp
AI agents use plugin_create 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 plugin_create is rated Medium
The tool creates new plugin specification files and persists them to disk in a system directory (~/.0n/plugins/). This is a reversible write operation (files can be deleted or edited later), not destructive. However, it modifies system configuration in a way that affects runtime behavior of the orchestrator, and an AI agent could create malicious or buggy plugins that impact system stability or security.
From the tool's definition Tool description states it "Generate[s] a new custom plugin spec" and "Saves to ~/.0n/plugins/" — these are create and write operations that modify the filesystem and configuration.
Attacks that exploit this kind of access
The rule that runs plugin_create 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_create, this is the rule to start with:
plugin_create 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 plugin_create call is checked against it from then on.
Questions about plugin_create
Generate a new custom plugin spec for a service not in the catalog. Auto-infers capabilities from endpoints and maps .0n canonical fields. Saves to ~/.0n/plugins/ for automatic loading. Example: plugin_create({ key:. 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 plugin_create: 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_create 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 plugin_create 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_create. 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_create 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