kya_reportBadgeOutcome · Payclaw MCP: Risk & Policy

WHAT IT DOES

What kya_reportBadgeOutcome does on Payclaw

AI agents use kya_reportBadgeOutcome to create or update resources in Payclaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Payclaw environment.

WHY IT NEEDS A POLICY

Why kya_reportBadgeOutcome needs a policy

The tool writes/records a badge presentation outcome to the system. Since it is deprecated and outcomes are now tracked automatically, its effective impact is minimal. No financial transaction, code execution, or destructive action is implied — it is a Write at low severity. Confidence is reduced due to the deprecated status and vague description.

From the tool's definition 'Report how the merchant responded when you presented your Badge' — this is a reporting/write action that records an outcome. Marked as DEPRECATED and outcomes now tracked automatically.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kya_reportBadgeOutcome Rate-limited

kya_reportBadgeOutcome stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kya_reportBadgeOutcome": {
      "limits": [
        {
          "counter": "kya_reportbadgeoutcome_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about kya_reportBadgeOutcome

What does the kya_reportBadgeOutcome tool do? +

[DEPRECATED — outcomes are now tracked automatically via the verify endpoint. This tool will be removed in a future version.] Report how the merchant responded when you presented your Badge. It is categorised as a Write tool in the Payclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kya_reportBadgeOutcome? +

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

What risk level is kya_reportBadgeOutcome? +

kya_reportBadgeOutcome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kya_reportBadgeOutcome? +

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

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

kya_reportBadgeOutcome is provided by the Payclaw MCP server (kyalabs-io/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.