# get_comments

A read tool on the WordPress MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_comments`. HTML page: https://policylayer.com/tools/beilunyang-wordpress-mcp-server/get-comments

## Facts

- Tool: `get_comments`
- Server: WordPress MCP Server (`beilunyang/wordpress-mcp-server`) — https://policylayer.com/tools/beilunyang-wordpress-mcp-server.md
- Homepage: https://github.com/beilunyang/wordpress-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "get_comments",
    "arguments": {}
  }
}
```

## Why get_comments is rated Low

The 'get_' prefix is a standard convention for retrieval/read operations. Combined with the WordPress context where this likely retrieves comments associated with posts, the tool performs data retrieval without side effects. Confidence is slightly reduced due to the empty description, but the naming and context provide clear signals of a read-only operation.

From the tool's own definition: "Tool name 'get_comments' indicates a retrieval operation. No description provided, but the naming convention and context as part of a WordPress content management system strongly suggests this queries/fetches comment data rather than modifying or deleting it."

## Use case

AI agents call get_comments to retrieve information from WordPress MCP Server 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 WordPress MCP Server:

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

## Other tools on WordPress MCP Server (3)

- `get_post_details` — Read — https://policylayer.com/tools/beilunyang-wordpress-mcp-server/get-post-details.md
- `search_posts` — Read — https://policylayer.com/tools/beilunyang-wordpress-mcp-server/search-posts.md
- `create_draft` — Write — https://policylayer.com/tools/beilunyang-wordpress-mcp-server/create-draft.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=beilunyang-wordpress-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/beilunyang-wordpress-mcp-server