audit_library
Audit the Elementor template library and report: total counts by type and status, templates without categories, draft templates, and templates not modified in >90 days.
This record as markdown: /tools/vamerli-elementify-mcp/audit-library.md
What audit_library does on Elementify MCP
AI agents call audit_library 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.
Why audit_library is rated Low
The audit_library tool retrieves and analyzes existing template library data to generate reports on template counts, categories, status, and modification dates. This is purely a querying/auditing operation with no side effects—it does not create, modify, delete, or execute any actions. It falls squarely into the Read category as a data retrieval and analysis function.
From the tool's definition Tool performs audit and reporting functions: 'report: total counts by type and status, templates without categories, draft templates, and templates not modified in >90 days.' These are read-only queries of template metadata with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs audit_library 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 audit_library, this is the rule to start with:
audit_library is read-only, so it stays allowed. 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 audit_library call is checked against it from then on.
Questions about audit_library
Audit the Elementor template library and report: total counts by type and status, templates without categories, draft templates, and templates not modified in >90 days. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.
Register the Elementify MCP server in PolicyLayer and add a rule for audit_library: 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.
audit_library is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the audit_library 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 audit_library. 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.
audit_library 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