seo_get_post_meta

Ruft SEO Meta-Tags eines Posts/einer Seite ab (Yoast, RankMath, oder Standard)

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/seo-get-post-meta.md

WHAT IT DOES

What seo_get_post_meta does on WordPress MCP Server

AI agents call seo_get_post_meta to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why seo_get_post_meta is rated Low

This tool queries and retrieves existing SEO metadata from WordPress posts or pages. It performs a read-only operation—no content is created, modified, deleted, or executed. The verb 'Ruft ab' (retrieves/fetches) confirms a passive data retrieval function. There are no side effects or state changes.

From the tool's definition Tool name 'seo_get_post_meta' and description 'Ruft SEO Meta-Tags eines Posts/einer Seite ab' (retrieves SEO meta tags of a post/page) indicate a retrieval operation with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo_get_post_meta safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_get_post_meta, this is the rule to start with:

seo_get_post_meta Allowed

seo_get_post_meta is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "seo_get_post_meta": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every seo_get_post_meta call is checked against it from then on.

FAQ

Questions about seo_get_post_meta

What does the seo_get_post_meta tool do? +

Ruft SEO Meta-Tags eines Posts/einer Seite ab (Yoast, RankMath, oder Standard). It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on seo_get_post_meta? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for seo_get_post_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 WordPress MCP Server. Nothing to install.

What risk level is seo_get_post_meta? +

seo_get_post_meta is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit seo_get_post_meta? +

Yes. Add a rate_limit block to the seo_get_post_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.

How do I block seo_get_post_meta completely? +

Set action: deny in the PolicyLayer policy for seo_get_post_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.

What MCP server provides seo_get_post_meta? +

seo_get_post_meta is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →