audit_postback · Xingzi MCP: Risk & Policy

WHAT IT DOES

What audit_postback does on Xingzi

AI agents invoke audit_postback to trigger actions in Xingzi. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why audit_postback needs a policy

This tool triggers downstream consequences: approving a submission enables reward payouts (financial adjacency) and rejecting one redistributes materials to other creators. It is not purely a read or write operation — it executes a workflow decision with significant, partially irreversible side effects (rejected creator loses claim; materials are redistributed).

From the tool's definition 审核 KOC 的回执。通过后可发放奖励，拒绝后素材释放给其他人领取 (Auditing KOC submissions — approval triggers reward eligibility, rejection releases materials to others)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

audit_postback Rate-limited

audit_postback stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audit_postback": {
      "limits": [
        {
          "counter": "audit_postback_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xingzi, so you can run agents against it safely.

FAQ

Questions about audit_postback

What does the audit_postback tool do? +

审核 KOC 的回执。通过后可发放奖励，拒绝后素材释放给其他人领取. It is categorised as a Execute tool in the Xingzi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on audit_postback? +

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

What risk level is audit_postback? +

audit_postback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit audit_postback? +

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

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

audit_postback is provided by the Xingzi MCP server (yylwdyx-commits/xingzi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.