High Risk →

add

Runs

How to control add ↓

What add does on Make

AI agents invoke add to trigger actions in Make. 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.

High Risk

Why add needs a policy

This tool is part of a Make/Just task runner MCP server. Running tasks via make/just executes arbitrary shell commands and scripts defined in Makefiles or Justfiles. The description is truncated ('Runs') but in context of a task runner, 'add' likely executes an add-related task (e.g., adding a dependency or component) by running shell commands.

From the tool's definition Tool name 'add' combined with server description 'MCP server for Make/Just task runners' — runs a Make/Just task

Documented attack patterns abuse exactly the kind of access add gives an agent:

How to control add

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for add:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add": {
      "limits": [
        {
          "counter": "add_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about add

What does the add tool do? +

Runs. It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on add? +

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

What risk level is add? +

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

Can I rate-limit add? +

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

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

add is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.