check_ai_content

Check whether text is likely AI-generated. Returns a score and analysis.

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/check-ai-content.md

WHAT IT DOES

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.

RISK

Why check_ai_content is rated Low

This tool performs content analysis and returns information without modifying, executing, deleting, or creating any data. It is purely informational—querying text and providing a classification result. No state is changed, no external operations are triggered, and no financial commitments are made.

From the tool's definition Tool description states it 'Check[s] whether text is likely AI-generated. Returns a score and analysis.' The verb 'check' and 'returns' indicate a read-only query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

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

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 check_ai_content call is checked against it from then on.

FAQ

Questions about check_ai_content

What does the check_ai_content tool do? +

Check whether text is likely AI-generated. Returns a score and analysis. 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 check_ai_content? +

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.

What risk level is check_ai_content? +

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

Can I rate-limit check_ai_content? +

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.

How do I block check_ai_content completely? +

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.

What MCP server provides check_ai_content? +

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.

KEEP EXPLORING

What check_ai_content does on Postking Mcp

Why check_ai_content is rated Low

The rule that runs check_ai_content safely

Questions about check_ai_content

More on Postking, and thousands of servers like it.