mcp_import_opencode_config · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What mcp_import_opencode_config does on LocalAnt

AI agents use mcp_import_opencode_config to create or update resources in LocalAnt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocalAnt environment.

WHY IT NEEDS A POLICY

Why mcp_import_opencode_config needs a policy

This tool performs a write operation by importing and registering new MCP servers into the local system configuration. While it states servers start disabled (a safety measure), the import action itself creates or modifies system state entries that can subsequently be re-imported, modified, or disabled—all reversible operations.

From the tool's definition The tool imports MCP servers from a config file and modifies the local MCP server state (servers "start disabled"), indicating reversible creation/modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_import_opencode_config Rate-limited

mcp_import_opencode_config 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": {
    "mcp_import_opencode_config": {
      "limits": [
        {
          "counter": "mcp_import_opencode_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocalAnt, so you can run agents against it safely.

FAQ

Questions about mcp_import_opencode_config

What does the mcp_import_opencode_config tool do? +

Import MCP servers from OpenCode config (opencode.json / opencode.jsonc). Imported servers start disabled. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mcp_import_opencode_config? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for mcp_import_opencode_config: 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 LocalAnt. Nothing to install.

What risk level is mcp_import_opencode_config? +

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

Can I rate-limit mcp_import_opencode_config? +

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

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

mcp_import_opencode_config is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.