engine_import
Import and map credentials from a .env, CSV, or JSON file. Auto-detects which of 26 supported services each credential belongs to. Returns mapped services with confidence scores and any unmapped variables. Example: engine_import({ source:
This record as markdown: /tools/io-github-0nork-0nmcp/engine-import.md
What engine_import does on 0nmcp
AI agents use engine_import 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 engine_import is rated Medium
This tool modifies system state by importing credentials into the engine, which constitutes a Write operation—it creates or registers new credential mappings. While it doesn't delete data, importing credentials could overwrite existing ones.
From the tool's definition Import and map credentials from a .env, CSV, or JSON file. Auto-detects which of 26 supported services each credential belongs to. Returns mapped services with confidence scores and any unmapped variables.
Attacks that exploit this kind of access
The rule that runs engine_import 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_import, this is the rule to start with:
engine_import 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 engine_import call is checked against it from then on.
Questions about engine_import
Import and map credentials from a .env, CSV, or JSON file. Auto-detects which of 26 supported services each credential belongs to. Returns mapped services with confidence scores and any unmapped variables. Example: engine_import({ source:. 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 engine_import: 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.
engine_import 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 engine_import 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 engine_import. 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.
engine_import 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