get_blog_status

Poll the async generation status of a blog article. Use the articleId returned by generate_blog_post. Status: pending | running | completed | failed.

SERVERPostking Mcp SOURCEpostking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/get-blog-status.md

WHAT IT DOES

What get_blog_status does on Postking Mcp

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

RISK

Why get_blog_status is rated Low

This tool only queries the current state of an existing asynchronous operation. It is a read-only operation with no side effects or modifications. Polling status information carries minimal risk even if called repeatedly, as it merely retrieves information about an in-progress or completed task.

From the tool's definition Tool polls and retrieves status of async blog generation ('Poll the async generation status'), returning one of four state values (pending | running | completed | failed). No data is created, modified, or deleted.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_blog_status safely

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

get_blog_status Allowed

get_blog_status 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": {
    "get_blog_status": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every get_blog_status call is checked against it from then on.

FAQ

Questions about get_blog_status

What does the get_blog_status tool do? +

Poll the async generation status of a blog article. Use the articleId returned by generate_blog_post. Status: pending | running | completed | failed. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_blog_status? +

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

What risk level is get_blog_status? +

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

Can I rate-limit get_blog_status? +

Yes. Add a rate_limit block to the get_blog_status 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 get_blog_status completely? +

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

get_blog_status is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What get_blog_status does on Postking Mcp

Why get_blog_status is rated Low

The rule that runs get_blog_status safely

Questions about get_blog_status

More on Postking, and thousands of servers like it.