export_build · Melo MCP: Risk & Policy

WHAT IT DOES

What export_build does on Melo

AI agents use export_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 export_build needs a policy

This tool creates new build snapshots and stores them persistently in a version-controlled library. It is reversible (snapshots can be deleted or replaced), so it does not qualify as Destructive. However, it goes beyond simple metadata—it saves instance hierarchies as JSON snapshots, making it a Write operation that modifies the state of the build library.

From the tool's definition Tool is described as 'Save a selection of instances as a versioned JSON snapshot in the build library' — it creates and stores a new versioned build entry in persistent storage (the build library). This is a data creation/write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_build Rate-limited

export_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": {
    "export_build": {
      "limits": [
        {
          "counter": "export_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 export_build

What does the export_build tool do? +

Save a selection of instances as a versioned JSON snapshot in the build library. Args: - path (string): Instance path to export - name (string): Name for the build entry - description (string, optional): Description Returns: { buildId, name, instanceCount }. 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 export_build? +

Register the Melo MCP server in PolicyLayer and add a rule for export_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 export_build? +

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

Can I rate-limit export_build? +

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

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

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