flush_elementor_cache
Flush Elementor CSS cache. Clears generated CSS files and forces regeneration on next page load.
This record as markdown: /tools/vamerli-elementify-mcp/flush-elementor-cache.md
What flush_elementor_cache does on Elementify MCP
AI agents invoke flush_elementor_cache to trigger actions in Elementify MCP. 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.
Why flush_elementor_cache is rated High
This tool clears cached CSS files and triggers regeneration, which is an operational action with side effects (cache invalidation, file deletion, forced recompilation). While it deletes generated/derived files, these are automatically regenerated on next load, making it non-destructive in a permanent sense.
From the tool's definition Flush Elementor CSS cache. Clears generated CSS files and forces regeneration on next page load.
Attacks that exploit this kind of access
The rule that runs flush_elementor_cache 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 flush_elementor_cache, this is the rule to start with:
flush_elementor_cache 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every flush_elementor_cache call is checked against it from then on.
Questions about flush_elementor_cache
Flush Elementor CSS cache. Clears generated CSS files and forces regeneration on next page load. It is categorised as a Execute tool in the Elementify MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Elementify MCP server in PolicyLayer and add a rule for flush_elementor_cache: 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.
flush_elementor_cache is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the flush_elementor_cache 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 flush_elementor_cache. 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.
flush_elementor_cache 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.
Across the catalogue