claudeus_wp_search__oembed_proxy
Get oEmbed data via proxy. Retrieve oEmbed data for external URLs through WordPress proxy.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-search--oembed-proxy.md
What claudeus_wp_search__oembed_proxy does on Claudeus WordPress MCP
AI agents call claudeus_wp_search__oembed_proxy 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_search__oembed_proxy is rated Low
The tool fetches oEmbed metadata (embed previews, structured data) from external URLs via WordPress proxy. This is fundamentally a retrieval operation (Read category). However, severity is elevated to medium rather than low because: (1) proxying through WordPress to external URLs creates potential for SSRF attacks if the URL parameter is not properly validated, allowing an AI agent to probe internal networks or…
From the tool's definition Tool name and description indicate it 'retrieves oEmbed data for external URLs through WordPress proxy' — a read-only query operation with no stated side effects.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_search__oembed_proxy 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_search__oembed_proxy, this is the rule to start with:
claudeus_wp_search__oembed_proxy 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_search__oembed_proxy call is checked against it from then on.
Questions about claudeus_wp_search__oembed_proxy
Get oEmbed data via proxy. Retrieve oEmbed data for external URLs through WordPress proxy. 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_search__oembed_proxy: 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_search__oembed_proxy 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_search__oembed_proxy 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_search__oembed_proxy. 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_search__oembed_proxy 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