AI agents use enable_plugin to create or update resources in FiftyOne MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FiftyOne MCP Server environment.
Enabling a plugin modifies system state (activating a previously disabled/inactive plugin), but it is reversible since plugins can be disabled again (as evidenced by the sibling 'disable_plugin' tool). This is a configuration change, not a destructive action, placing it in the Write category. Misuse could activate unintended plugins affecting system behavior, warranting medium severity.
From the tool's definition Enables a downloaded FiftyOne plugin
Documented attack patterns abuse exactly the kind of access enable_plugin gives an agent:
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 enable_plugin:
{
"version": "1",
"default": "deny",
"tools": {
"enable_plugin": {
"limits": [
{
"counter": "enable_plugin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}enable_plugin 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.
Free to start. No card required.
Enables a downloaded FiftyOne plugin,. It is categorised as a Write tool in the FiftyOne MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FiftyOne MCP Server MCP server in PolicyLayer and add a rule for enable_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.
enable_plugin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_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.
Set action: deny in the PolicyLayer policy for enable_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.
enable_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.
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.