mcp_import_all_agent_configs · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What mcp_import_all_agent_configs does on LocalAnt

AI agents use mcp_import_all_agent_configs 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_all_agent_configs needs a policy

This tool creates or adds MCP server configurations to the local system by importing them from external config sources. While the servers start disabled (limiting immediate impact), the import operation itself writes configuration data to the system and extends its capabilities. This is reversible (configs can be removed or disabled), so it is Write rather than Destructive.

From the tool's definition Tool description states 'Import MCP servers from Claude Code, Codex, and OpenCode configs. Imported servers start disabled.' The term 'Import' indicates creation or addition of configuration data to the system; this is a reversible write operation that…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_import_all_agent_configs Rate-limited

mcp_import_all_agent_configs 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_all_agent_configs": {
      "limits": [
        {
          "counter": "mcp_import_all_agent_configs_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_all_agent_configs

What does the mcp_import_all_agent_configs tool do? +

Import MCP servers from Claude Code, Codex, and OpenCode configs. 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_all_agent_configs? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for mcp_import_all_agent_configs: 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_all_agent_configs? +

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

Can I rate-limit mcp_import_all_agent_configs? +

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

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

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