build_catalog_payload

Server Mr Magic mr-magic-mcp-server

Category Execute

Risk class High

Parameters 00 required

WHAT IT DOES

What build_catalog_payload does on Mr Magic

AI agents invoke build_catalog_payload to trigger actions in Mr Magic. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why build_catalog_payload needs a policy

build_catalog_payload triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_catalog_payload Rate-limited

build_catalog_payload stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_catalog_payload": {
      "limits": [
        {
          "counter": "build_catalog_payload_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about build_catalog_payload

What does the build_catalog_payload tool do? +

Return a compact payload suitable for Airtable inserts/exports. Accepts track metadata or an exact provider reference from the MCP search tools. For large lyrics, send object args and use omitInlineLyrics + lyricsPayloadMode to avoid JSON truncation in downstream automations. Airtable-safe compact mode can auto-promote payload transport to reference. It is categorised as a Execute tool in the Mr Magic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_catalog_payload? +

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

What risk level is build_catalog_payload? +

build_catalog_payload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_catalog_payload? +

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

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

build_catalog_payload is provided by the Mr Magic MCP server (mr-magic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.