engine_export

SERVER0nmcp SOURCE0nmcp

Medium RISK CLASS

Category Write

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/engine-export.md

WHAT IT DOES

What engine_export does on 0nmcp

AI agents use engine_export 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.

RISK

Why engine_export is rated Medium

This tool creates and outputs a new artifact (encrypted bundle file) containing configuration data from connected services. While the operation itself is reversible (exported bundles do not modify the source system), the export produces a new data object representing system configurations.

From the tool's definition Tool explicitly performs 'Export' operation creating a 'portable .0n bundle file' and involves 'platform configs for all major AI tools'; description indicates data is being packaged and encrypted for portability rather than merely queried.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

engine_export Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "engine_export": {
      "limits": [
        {
          "counter": "engine_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about engine_export

What does the engine_export tool do? +

Export connected services as a portable .0n bundle file. The bundle is encrypted with a passphrase (portable — works on any machine). Includes platform configs for all major AI tools. Example: engine_export({ passphrase:. 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.

How do I enforce a policy on engine_export? +

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

engine_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit engine_export? +

Yes. Add a rate_limit block to the engine_export 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 engine_export completely? +

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

engine_export 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →