# wavexis_get_response_body

Get the body of a network response by ID (W3).

Agent View of the PolicyLayer registry record for `wavexis_get_response_body`. HTML page: https://policylayer.com/tools/wavexis-mcp/wavexis-get-response-body

## Facts

- Tool: `wavexis_get_response_body`
- Server: Wavexis (`MathiasPaulenko/wavexis-mcp`) — https://policylayer.com/tools/wavexis-mcp.md
- Homepage: https://github.com/MathiasPaulenko/wavexis-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why wavexis_get_response_body is rated Low

This tool retrieves network response data by ID. It is a read-only operation that queries and returns existing data without modifying, deleting, or executing code. However, the severity is medium rather than low because network response bodies may contain sensitive information (authentication tokens, API keys, PII, secrets) that could be exposed if an agent misuses this tool to inspect responses it shouldn't access.

From the tool's own definition: "Tool name 'wavexis_get_response_body' and description 'Get the body of a network response by ID' indicate retrieval of data with no side effects."

## Use case

AI agents call wavexis_get_response_body to retrieve information from Wavexis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Wavexis:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wavexis_get_response_body": {}
  }
}
```

## Other tools on Wavexis (194)

- `wavexis_cache_storage_delete` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-cache-storage-delete.md
- `wavexis_cookies_clear` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-cookies-clear.md
- `wavexis_cookies_delete` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-cookies-delete.md
- `wavexis_dom_remove` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-dom-remove.md
- `wavexis_extension_uninstall` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-extension-uninstall.md
- `wavexis_indexeddb_clear` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-indexeddb-clear.md
- `wavexis_localstorage_clear` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-localstorage-clear.md
- `wavexis_localstorage_delete` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-localstorage-delete.md
- `wavexis_overlay_clear` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-overlay-clear.md
- `wavexis_reset_permissions` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-reset-permissions.md
- `wavexis_sessionstorage_clear` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-sessionstorage-clear.md
- `wavexis_sessionstorage_delete` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-sessionstorage-delete.md
- `wavexis_webauthn_remove_credential` — Destructive — https://policylayer.com/tools/wavexis-mcp/wavexis-webauthn-remove-credential.md
- `wavexis_act` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-act.md
- `wavexis_activate_tab` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-activate-tab.md
- `wavexis_animation_pause` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-animation-pause.md
- `wavexis_animation_play` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-animation-play.md
- `wavexis_animation_set_rate` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-animation-set-rate.md
- `wavexis_back` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-back.md
- `wavexis_block_requests` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-block-requests.md
- `wavexis_bluetooth_adapter_state` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-bluetooth-adapter-state.md
- `wavexis_bluetooth_device_connect` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-bluetooth-device-connect.md
- `wavexis_bluetooth_device_disconnect` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-bluetooth-device-disconnect.md
- `wavexis_browser_context_create` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-browser-context-create.md
- `wavexis_cast_start` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-cast-start.md
- `wavexis_cast_stop` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-cast-stop.md
- `wavexis_check` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-check.md
- `wavexis_click` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-click.md
- `wavexis_crawl` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-crawl.md
- `wavexis_debug_pause` — Execute — https://policylayer.com/tools/wavexis-mcp/wavexis-debug-pause.md
- …and 164 more: https://policylayer.com/tools/wavexis-mcp.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=wavexis-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/wavexis-mcp