detect_uae

Detect Ultimate Addons for Elementor (Free/Pro), version, tier, and widget count.

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/detect-uae.md

WHAT IT DOES

What detect_uae does on Elementify MCP

AI agents call detect_uae 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 detect_uae is rated Low

This tool performs reconnaissance on the WordPress/Elementor environment by reading addon information. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It falls squarely into the Read category as a query/detection operation that returns system state information.

From the tool's definition The tool 'detect_uae' is described as detecting Ultimate Addons for Elementor version, tier, and widget count.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_uae 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 detect_uae, this is the rule to start with:

detect_uae Allowed

detect_uae 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": {
    "detect_uae": {}
  }
}

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 detect_uae call is checked against it from then on.

FAQ

Questions about detect_uae

What does the detect_uae tool do? +

Detect Ultimate Addons for Elementor (Free/Pro), version, tier, and widget count. 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 detect_uae? +

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

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

Can I rate-limit detect_uae? +

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

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

detect_uae 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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