High Risk →

get

Downloads and installs Go packages and their dependencies.

How to control get ↓

What get does on Make

AI agents invoke get 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 get needs a policy

This tool downloads code from the internet and installs it into the system environment. This is an Execute-class action because it triggers external network operations and modifies the local system by installing packages. The blast radius is high because an AI agent could install malicious or unintended packages, potentially compromising the system.

From the tool's definition Downloads and installs Go packages and their dependencies

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

How to control get

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 get:

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

get 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 get

What does the get tool do? +

Downloads and installs Go packages and their dependencies. 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 get? +

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

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

Can I rate-limit get? +

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

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

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