list_active_addons

List all active Elementor add‑on plugins detected by the adapter framework.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vamerli-elementify-mcp/list-active-addons.md

WHAT IT DOES

What list_active_addons does on Elementify MCP

AI agents call list_active_addons to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_active_addons is rated Low

This tool retrieves and enumerates information about currently active Elementor add-on plugins. It performs a query operation with no capability to modify, delete, or execute code. The information retrieved is already known to the system and merely being reported. This is a straightforward Read operation with minimal risk—the worst misuse would be reconnaissance to understand the addon ecosystem, which is low-impact.

From the tool's definition Tool name is 'list_active_addons' and description states 'List all active Elementor add‑on plugins detected by the adapter framework.' The verb 'List' indicates data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_active_addons safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_active_addons, this is the rule to start with:

list_active_addons Allowed

list_active_addons is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_active_addons": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every list_active_addons call is checked against it from then on.

FAQ

Questions about list_active_addons

What does the list_active_addons tool do? +

List all active Elementor add‑on plugins detected by the adapter framework. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_active_addons? +

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

What risk level is list_active_addons? +

list_active_addons is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_active_addons? +

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

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

list_active_addons is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 269 Elementify tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →