get_site_info
Get information about a WordPress site running the Elementeer plugin: WP version, Elementor version, activation mode, template count, and available capabilities.
This record as markdown: /tools/vamerli-elementify-mcp/get-site-info.md
What get_site_info does on Elementify MCP
AI agents call get_site_info 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_site_info is rated Low
This tool queries and retrieves metadata about a WordPress installation and its Elementor plugin configuration. It has no side effects, does not modify data, and does not trigger external operations. It is a straightforward read operation that could be used by an AI agent to understand the system state before performing other actions, with minimal risk even if executed without proper authorization.
From the tool's definition Tool performs information retrieval only: 'Get information about a WordPress site' with outputs limited to 'WP version, Elementor version, activation mode, template count, and available capabilities.' No modification, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs get_site_info 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_site_info, this is the rule to start with:
get_site_info 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_site_info call is checked against it from then on.
Questions about get_site_info
Get information about a WordPress site running the Elementeer plugin: WP version, Elementor version, activation mode, template count, and available capabilities. 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_site_info: 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_site_info 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_site_info 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_site_info. 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_site_info 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