# rest_api_execute

Führt eine beliebige WordPress REST API Funktion aus. Unterstützt GET, POST, PUT, PATCH und DELETE Operationen.

Agent View of the PolicyLayer registry record for `rest_api_execute`. HTML page: https://policylayer.com/tools/c-sakel-wp-mcp-server/rest-api-execute

## Facts

- Tool: `rest_api_execute`
- Server: WordPress MCP Server (`c-sakel/wp-mcp-server`) — https://policylayer.com/tools/c-sakel-wp-mcp-server.md
- Homepage: https://github.com/c-sakel/wp-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "rest_api_execute",
    "arguments": {}
  }
}
```

## Why rest_api_execute is rated High

This tool allows execution of arbitrary WordPress REST API operations across all HTTP methods. While it includes destructive operations (DELETE), the primary risk is that it can execute any WordPress API function with parameters controlled by the AI agent, making outcomes dependent on arguments. This is the Execute category (code/command execution with argument-dependent effects).

From the tool's own definition: "Tool description states it 'executes arbitrary WordPress REST API function' and supports GET, POST, PUT, PATCH and DELETE operations. The word 'beliebige' (arbitrary) is key—this permits any API call."

## Use case

AI agents invoke rest_api_execute to trigger actions in WordPress MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches WordPress MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rest_api_execute": {
      "limits": [
        {
          "counter": "rest_api_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on WordPress MCP Server (191)

- `admin_delete_app_password` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/admin-delete-app-password.md
- `admin_delete_user` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/admin-delete-user.md
- `comment_delete` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/comment-delete.md
- `image_delete_unused` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/image-delete-unused.md
- `revision_cleanup` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/revision-cleanup.md
- `revision_delete` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/revision-delete.md
- `woo_delete_product` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/woo-delete-product.md
- `wp_delete_post` — Destructive — https://policylayer.com/tools/c-sakel-wp-mcp-server/wp-delete-post.md
- `image_regenerate_thumbnails` — Execute — https://policylayer.com/tools/c-sakel-wp-mcp-server/image-regenerate-thumbnails.md
- `jwt_authenticate` — Execute — https://policylayer.com/tools/c-sakel-wp-mcp-server/jwt-authenticate.md
- `rest_api_batch` — Execute — https://policylayer.com/tools/c-sakel-wp-mcp-server/rest-api-batch.md
- `a11y_check_color_contrast` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-check-color-contrast.md
- `a11y_check_forms` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-check-forms.md
- `a11y_check_images` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-check-images.md
- `a11y_check_links` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-check-links.md
- `a11y_check_page_structure` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-check-page-structure.md
- `a11y_generate_report` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/a11y-generate-report.md
- `acf_bulk_get_fields` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-bulk-get-fields.md
- `acf_get_field_group` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-field-group.md
- `acf_get_flexible_layouts` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-flexible-layouts.md
- `acf_get_options` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-options.md
- `acf_get_post_fields` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-post-fields.md
- `acf_get_repeater_rows` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-repeater-rows.md
- `acf_get_term_fields` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-term-fields.md
- `acf_get_user_fields` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-get-user-fields.md
- `acf_list_field_groups` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-list-field-groups.md
- `acf_list_field_types` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/acf-list-field-types.md
- `admin_export_content` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/admin-export-content.md
- `admin_flush_cache` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/admin-flush-cache.md
- `admin_get_option` — Read — https://policylayer.com/tools/c-sakel-wp-mcp-server/admin-get-option.md
- …and 161 more: https://policylayer.com/tools/c-sakel-wp-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=c-sakel-wp-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/c-sakel-wp-mcp-server