ux_mobile_friendliness

Analysiert den Content auf Mobile-Optimierung

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/ux-mobile-friendliness.md

WHAT IT DOES

What ux_mobile_friendliness does on WordPress MCP Server

AI agents call ux_mobile_friendliness 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 ux_mobile_friendliness is rated Low

This tool analyzes and reports on mobile-friendliness characteristics of WordPress content. It retrieves or queries data about mobile optimization status without modifying content, executing code, or triggering side effects. Similar to sibling tools like a11y_check_* which are clearly audit/analysis functions.

From the tool's definition Tool name contains 'check' pattern (ux_mobile_friendliness) and description states 'Analysiert' (analyzes/checks) the content for mobile optimization. No modification, deletion, or execution of external operations is indicated.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ux_mobile_friendliness 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 ux_mobile_friendliness, this is the rule to start with:

ux_mobile_friendliness Allowed

ux_mobile_friendliness 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": {
    "ux_mobile_friendliness": {}
  }
}

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 ux_mobile_friendliness call is checked against it from then on.

FAQ

Questions about ux_mobile_friendliness

What does the ux_mobile_friendliness tool do? +

Analysiert den Content auf Mobile-Optimierung. 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 ux_mobile_friendliness? +

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

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

Can I rate-limit ux_mobile_friendliness? +

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

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

ux_mobile_friendliness 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

The MCP Attack Database →

Guides

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