import_build · Melo MCP: Risk & Policy

WHAT IT DOES

What import_build does on Melo

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

WHY IT NEEDS A POLICY

Why import_build needs a policy

The tool performs a write operation by importing and materializing a saved build into the active Studio project. While not destructive (the operation is reversible by undoing or deleting the imported content), it modifies the state of the development environment.

From the tool's definition Tool 'import_build' loads a saved build from the library into Studio, which creates or modifies the development environment by introducing external build data into the current workspace.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_build Rate-limited

import_build 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": {
    "import_build": {
      "limits": [
        {
          "counter": "import_build_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 Melo, so you can run agents against it safely.

FAQ

Questions about import_build

What does the import_build tool do? +

Load a saved build from the library into Studio. Args: - name (string): Build name to import - parent (string, optional): Parent path (default:. It is categorised as a Write tool in the Melo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_build? +

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

What risk level is import_build? +

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

Can I rate-limit import_build? +

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

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

import_build is provided by the Melo MCP server (yannyhl/linkedsword-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.