AI agents call elementor_get_template to retrieve information from ItchWPMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads template information from the WordPress/Elementor system. It returns data about templates (JSON content and structure summary) with no side effects, no data modification, and no actions taken beyond retrieval. The purpose is explicit inspection before other operations. This is a straightforward Read category tool with low severity since it only exposes data visibility.
From the tool's definition Tool retrieves and inspects Elementor template data without modifying anything. Description states 'Get the full data' and 'Use to inspect before applying' — purely informational/query operations.
Attacks that exploit this kind of access
Get the full data for an Elementor template including its Elementor JSON content and a structure summary. Use to inspect before applying to a page. It is categorised as a Read tool in the ItchWPMCP MCP Server, which means it retrieves data without modifying state.
Register the ItchWP MCP server in PolicyLayer and add a rule for elementor_get_template: 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 ItchWPMCP. Nothing to install.
elementor_get_template 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 elementor_get_template 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 elementor_get_template. 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.
elementor_get_template is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →