check_ai_content
Diagnostic: scores how generic/templated a piece of text reads and returns an analysis of which passages feel machine-written. Use it to find weak writing for a human to revise — not as a target to optimise against by re-running humanize_text until the score drops.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/check-ai-content.md
What check_ai_content does on Postking Mcp
AI agents call check_ai_content 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.
Why check_ai_content is rated Low
Tool analyzes content and returns scoring/analysis only; produces no side effects or data modifications.
From the tool's definition scores text, returns analysis, diagnostic tool, no modifications
Attacks that exploit this kind of access
The rule that runs check_ai_content 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 check_ai_content, this is the rule to start with:
check_ai_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every check_ai_content call is checked against it from then on.
Questions about check_ai_content
Diagnostic: scores how generic/templated a piece of text reads and returns an analysis of which passages feel machine-written. Use it to find weak writing for a human to revise — not as a target to optimise against by re-running humanize_text until the score drops. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for check_ai_content: 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.
check_ai_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_ai_content 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.
Set action: deny in the PolicyLayer policy for check_ai_content. 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.
check_ai_content 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.
More on Postking, and thousands of servers like it.
This server
Across the catalogue