New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

claudeus_wp_widgets__get_widgets

Get all widgets. List all widget instances across all sidebars with their settings and rendered output.

SERVERClaudeus WordPress MCP SOURCEdeus-h/claudeus-wp-mcp
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/deus-h-claudeus-wp-mcp/claudeus-wp-widgets--get-widgets.md

What claudeus_wp_widgets__get_widgets does on Claudeus WordPress MCP

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

This tool retrieves and lists widget configuration data without any side effects. It does not create, modify, delete, or execute any operations — it only queries and returns existing widget information from the WordPress site. This is a straightforward Read operation with minimal risk.

From the tool's definition Tool name contains 'get_widgets' and description states 'List all widget instances across all sidebars with their settings and rendered output' — purely retrieval with no modification.

Questions about claudeus_wp_widgets__get_widgets

What does the claudeus_wp_widgets__get_widgets tool do? +

Get all widgets. List all widget instances across all sidebars with their settings and rendered output. It is categorised as a Read tool in the Claudeus WordPress MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on claudeus_wp_widgets__get_widgets? +

Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_widgets__get_widgets: 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.

What risk level is claudeus_wp_widgets__get_widgets? +

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

Can I rate-limit claudeus_wp_widgets__get_widgets? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claudeus WordPress's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.