import_premium_library_asset
Import a curated Elementeer Premium Library asset into the local Elementor Library on the current site. This is an Advanced-only execution seam that uses the dedicated local library/import endpoint and does not imply cloud sync or Studio delivery behavior.
This record as markdown: /tools/vamerli-elementify-mcp/import-premium-library-asset.md
What import_premium_library_asset does on Elementify MCP
AI agents use import_premium_library_asset to create or update resources in Elementify MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elementify MCP environment.
Why import_premium_library_asset is rated Medium
This tool creates or adds new assets (templates/library items) to a WordPress site's Elementor library. While it modifies data, the operation is reversible—imported assets can be deleted or replaced. It does not execute arbitrary code, delete data irreversibly, or move money. The 'Advanced-only' restriction and mention of a 'dedicated local library/import endpoint' suggest it operates within constrained scope.
From the tool's definition The tool name and description indicate it 'Import[s]' and creates/adds assets into 'the local Elementor Library on the current site.' The description specifies this uses an 'import endpoint,' which modifies the local library state by adding new assets.
Attacks that exploit this kind of access
The rule that runs import_premium_library_asset 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 import_premium_library_asset, this is the rule to start with:
import_premium_library_asset 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every import_premium_library_asset call is checked against it from then on.
Questions about import_premium_library_asset
Import a curated Elementeer Premium Library asset into the local Elementor Library on the current site. This is an Advanced-only execution seam that uses the dedicated local library/import endpoint and does not imply cloud sync or Studio delivery behavior. It is categorised as a Write tool in the Elementify MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Elementify MCP server in PolicyLayer and add a rule for import_premium_library_asset: 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.
import_premium_library_asset 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 import_premium_library_asset 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 import_premium_library_asset. 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.
import_premium_library_asset 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.
More on Elementify, and thousands of servers like it.
This server
Across the catalogue