claudeus_wp_menus__get_menu_items
Get a list of menu items. Retrieve items from all menus or filter by specific menu ID.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-menus--get-menu-items.md
What claudeus_wp_menus__get_menu_items does on Claudeus WordPress MCP
AI agents call claudeus_wp_menus__get_menu_items to retrieve information from Claudeus WordPress MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why claudeus_wp_menus__get_menu_items is rated Low
This tool retrieves menu structure data from a WordPress site. It performs a query operation that has no side effects—it does not create, modify, delete, execute code, or move money. The blast radius of misuse is minimal; an agent could only read menu information already accessible through standard WordPress REST API endpoints. This is a standard Read category tool.
From the tool's definition Tool name includes 'get_menu_items' and description states 'Get a list of menu items. Retrieve items from all menus or filter by specific menu ID.' The verb 'Get' and 'Retrieve' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_menus__get_menu_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_menus__get_menu_items, this is the rule to start with:
claudeus_wp_menus__get_menu_items is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_menus__get_menu_items call is checked against it from then on.
Questions about claudeus_wp_menus__get_menu_items
Get a list of menu items. Retrieve items from all menus or filter by specific menu ID. It is categorised as a Read tool in the Claudeus WordPress MCP MCP Server, which means it retrieves data without modifying state.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_menus__get_menu_items: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_menus__get_menu_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the claudeus_wp_menus__get_menu_items 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.
Set action: deny in the PolicyLayer policy for claudeus_wp_menus__get_menu_items. 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.
claudeus_wp_menus__get_menu_items is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
This server
Across the catalogue