plugin_execute

Execute a plugin endpoint with automatic .0n field resolution. Accepts canonical .0n fields (email.0n, fullname.0n, etc.) and auto-translates to the service

SERVER0nmcp SOURCE0nmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/plugin-execute.md

WHAT IT DOES

What plugin_execute does on 0nmcp

AI agents invoke plugin_execute 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.

RISK

Why plugin_execute is rated High

This tool triggers execution of arbitrary plugin endpoints with automatic parameter resolution. The dynamic field translation and service abstraction create significant risk of unintended side effects depending on which plugin endpoint is invoked and what fields are passed.

From the tool's definition Tool name is 'plugin_execute' with description stating 'Execute a plugin endpoint'. The verb 'Execute' combined with 'automatic .0n field resolution' and 'auto-translates to the service' indicates the tool runs external plugin code with dynamic field mapping.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs plugin_execute 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_execute, this is the rule to start with:

plugin_execute Rate-limited

plugin_execute 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plugin_execute": {
      "limits": [
        {
          "counter": "plugin_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every plugin_execute call is checked against it from then on.

FAQ

Questions about plugin_execute

What does the plugin_execute tool do? +

Execute a plugin endpoint with automatic .0n field resolution. Accepts canonical .0n fields (email.0n, fullname.0n, etc.) and auto-translates to the service. 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.

How do I enforce a policy on plugin_execute? +

Register the 0n MCP server in PolicyLayer and add a rule for plugin_execute: 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.

What risk level is plugin_execute? +

plugin_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit plugin_execute? +

Yes. Add a rate_limit block to the plugin_execute 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.

How do I block plugin_execute completely? +

Set action: deny in the PolicyLayer policy for plugin_execute. 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.

What MCP server provides plugin_execute? +

plugin_execute 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.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →