get_performance_report
Get a comprehensive performance and health report: CSS printing method, DOM size, asset optimization, cache status, Elementor version, PHP info, object cache, autoloaded options, database stats, enqueued assets, and render-blocking resources.
This record as markdown: /tools/vamerli-elementify-mcp/get-performance-report.md
What get_performance_report does on Elementify MCP
AI agents call get_performance_report 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 get_performance_report is rated Low
This tool performs read-only queries of system diagnostics and configuration metadata. It gathers performance metrics and health information about the Elementor environment without modifying any data, executing code, or triggering external operations. The information returned is observational only.
From the tool's definition Tool retrieves diagnostic data: CSS printing method, DOM size, asset optimization, cache status, Elementor version, PHP info, object cache, autoloaded options, database stats, enqueued assets, and render-blocking resources.
Attacks that exploit this kind of access
The rule that runs get_performance_report 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 get_performance_report, this is the rule to start with:
get_performance_report 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 get_performance_report call is checked against it from then on.
Questions about get_performance_report
Get a comprehensive performance and health report: CSS printing method, DOM size, asset optimization, cache status, Elementor version, PHP info, object cache, autoloaded options, database stats, enqueued assets, and render-blocking resources. 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 get_performance_report: 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.
get_performance_report 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 get_performance_report 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 get_performance_report. 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.
get_performance_report 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