High Risk →

download_plugin

Downloads and installs a FiftyOne plugin

How to control download_plugin ↓

What download_plugin does on FiftyOne MCP Server

AI agents invoke download_plugin to trigger actions in FiftyOne MCP Server. 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 download_plugin needs a policy

This tool downloads and installs external code (a plugin) into the FiftyOne environment. Installing a plugin executes external code and modifies the system state in a significant way. While not purely destructive, the act of installing arbitrary third-party plugins poses high risk as it introduces executable code that could have broad side effects.

From the tool's definition Downloads and installs a FiftyOne plugin

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

How to control download_plugin

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

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

download_plugin 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 FiftyOne MCP Server — 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 download_plugin

What does the download_plugin tool do? +

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

How do I enforce a policy on download_plugin? +

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

What risk level is download_plugin? +

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

Can I rate-limit download_plugin? +

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

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

download_plugin is provided by the FiftyOne MCP Server MCP server (voxel51/fiftyone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FiftyOne MCP Server tool call.

Start from FiftyOne MCP Server, 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.

47 FiftyOne MCP Server 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.