New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

flush_elementor_cache

Flush Elementor CSS cache. Clears generated CSS files and forces regeneration on next page load.

SERVERElementify MCP SOURCEvamerli/elementify-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about flush_elementor_cache

What does the flush_elementor_cache tool do? +

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.

How do I enforce a policy on flush_elementor_cache? +

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.

What risk level is flush_elementor_cache? +

flush_elementor_cache is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit flush_elementor_cache? +

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.

How do I block flush_elementor_cache completely? +

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.

What MCP server provides flush_elementor_cache? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Elementify's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.