wordpress_assign_menu_to_location · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_assign_menu_to_location does on WordPress MCP Server

AI agents use wordpress_assign_menu_to_location 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_assign_menu_to_location needs a policy

Assigning a menu to a location modifies WordPress site structure and navigation configuration, affecting all site visitors. This is reversible (can reassign or unassign), so it falls under Write rather than Destructive. Severity is medium because incorrect menu assignments could degrade user experience and site navigation, but the change is non-destructive and can be undone.

From the tool's definition Tool name 'wordpress_assign_menu_to_location' indicates assignment/modification of menu configuration. The 'assign' verb and lack of destructive language ('delete', 'remove', 'purge') suggest reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_assign_menu_to_location Rate-limited

wordpress_assign_menu_to_location 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_assign_menu_to_location": {
      "limits": [
        {
          "counter": "wordpress_assign_menu_to_location_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_assign_menu_to_location

What does the wordpress_assign_menu_to_location tool do? +

wordpress_assign_menu_to_location. 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_assign_menu_to_location? +

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

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

Can I rate-limit wordpress_assign_menu_to_location? +

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

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

wordpress_assign_menu_to_location 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.