wordpress_set_twitter_cards · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_set_twitter_cards does on WordPress MCP Server

AI agents use wordpress_set_twitter_cards to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.

WHY IT NEEDS A POLICY

Why wordpress_set_twitter_cards needs a policy

This tool creates or modifies Twitter Card metadata (a reversible configuration change) on WordPress, which is characteristic of a Write operation. It does not execute arbitrary code, delete data irreversibly, move money, or require external execution. The medium severity reflects the scope of impact being limited to social media metadata configuration, though misuse could affect SEO and site presentation.

From the tool's definition Tool name 'wordpress_set_twitter_cards' indicates modification of Twitter Card metadata settings on a WordPress site.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_set_twitter_cards Rate-limited

wordpress_set_twitter_cards stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_set_twitter_cards": {
      "limits": [
        {
          "counter": "wordpress_set_twitter_cards_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_set_twitter_cards

What does the wordpress_set_twitter_cards tool do? +

wordpress_set_twitter_cards. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wordpress_set_twitter_cards? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_set_twitter_cards: 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 wordpress_set_twitter_cards? +

wordpress_set_twitter_cards is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wordpress_set_twitter_cards? +

Yes. Add a rate_limit block to the wordpress_set_twitter_cards 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 wordpress_set_twitter_cards completely? +

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

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