get_seo_meta
Get SEO meta (title, description, focus keyword) for a post/page. Auto-detects active SEO plugin: Yoast SEO, Rank Math, SEOPress, or All‑In‑One SEO.
This record as markdown: /tools/vamerli-elementify-mcp/get-seo-meta.md
What get_seo_meta does on Elementify MCP
AI agents call get_seo_meta 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_seo_meta is rated Low
This tool retrieves SEO metadata from posts/pages without creating, modifying, deleting, or executing any operations. It queries configuration data from active SEO plugins and returns read-only information. No side effects or irreversible actions are possible.
From the tool's definition Tool description states 'Get SEO meta (title, description, focus keyword) for a post/page' - uses verb 'Get' indicating data retrieval with no modification. Returns metadata only (title, description, focus keyword) from existing SEO plugin configurations.
Attacks that exploit this kind of access
The rule that runs get_seo_meta 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_seo_meta, this is the rule to start with:
get_seo_meta 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_seo_meta call is checked against it from then on.
Questions about get_seo_meta
Get SEO meta (title, description, focus keyword) for a post/page. Auto-detects active SEO plugin: Yoast SEO, Rank Math, SEOPress, or All‑In‑One SEO. 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_seo_meta: 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_seo_meta 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_seo_meta 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_seo_meta. 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_seo_meta 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