comment_get_pending_count

Zählt Kommentare nach Status

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/comment-get-pending-count.md

WHAT IT DOES

What comment_get_pending_count does on WordPress MCP Server

AI agents call comment_get_pending_count 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.

RISK

Why comment_get_pending_count is rated Low

The tool counts/retrieves comment statistics by status, which is a pure read operation. No data is modified, created, or deleted.

From the tool's definition 'Zählt Kommentare nach Status' means 'Counts comments by status' in German — a read/query operation with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comment_get_pending_count safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comment_get_pending_count, this is the rule to start with:

comment_get_pending_count Allowed

comment_get_pending_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comment_get_pending_count": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every comment_get_pending_count call is checked against it from then on.

FAQ

Questions about comment_get_pending_count

What does the comment_get_pending_count tool do? +

Zählt Kommentare nach Status. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on comment_get_pending_count? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for comment_get_pending_count: 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 WordPress MCP Server. Nothing to install.

What risk level is comment_get_pending_count? +

comment_get_pending_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit comment_get_pending_count? +

Yes. Add a rate_limit block to the comment_get_pending_count 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.

How do I block comment_get_pending_count completely? +

Set action: deny in the PolicyLayer policy for comment_get_pending_count. 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.

What MCP server provides comment_get_pending_count? +

comment_get_pending_count is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →