mcp_assign_menu_location

Assign a menu to a registered theme location (see mcp_get_menu_locations); menu_id 0 unassigns

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-assign-menu-location.md

WHAT IT DOES

What mcp_assign_menu_location does on Wordpress

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

RISK

Why mcp_assign_menu_location is rated Medium

Reversibly modifies WordPress menu assignments affecting site navigation structure.

From the tool's definition Assign a menu to a registered theme location; menu_id 0 unassigns

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_assign_menu_location safely

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

mcp_assign_menu_location Rate-limited

mcp_assign_menu_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": {
    "mcp_assign_menu_location": {
      "limits": [
        {
          "counter": "mcp_assign_menu_location_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mcp_assign_menu_location

What does the mcp_assign_menu_location tool do? +

Assign a menu to a registered theme location (see mcp_get_menu_locations); menu_id 0 unassigns. It is categorised as a Write tool in the Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mcp_assign_menu_location? +

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

What risk level is mcp_assign_menu_location? +

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

Can I rate-limit mcp_assign_menu_location? +

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

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

mcp_assign_menu_location is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →