claudeus_wp_widgets__get_widget
Get a specific widget by ID. View widget type, settings, sidebar placement, and rendered HTML.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-widgets--get-widget.md
What claudeus_wp_widgets__get_widget does on Claudeus WordPress MCP
AI agents call claudeus_wp_widgets__get_widget 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_widget is rated Low
This tool retrieves widget information and renders HTML for display purposes. It performs a query operation with no capacity to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker gains visibility into widget configuration but cannot alter site behavior or access sensitive data beyond what widgets already expose.
From the tool's definition Tool name contains 'get_widget' and description states 'Get a specific widget by ID. View widget type, settings, sidebar placement, and rendered HTML.' The verb 'Get' and 'View' indicate read-only retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_widgets__get_widget 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_widgets__get_widget, this is the rule to start with:
claudeus_wp_widgets__get_widget 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_widgets__get_widget call is checked against it from then on.
Questions about claudeus_wp_widgets__get_widget
Get a specific widget by ID. View widget type, settings, sidebar placement, and rendered HTML. 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_widgets__get_widget: 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_widgets__get_widget 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_widgets__get_widget 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_widgets__get_widget. 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_widgets__get_widget 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