kyc_screener_batch_result
Poll the result of a kyc_screener_batch job. Returns status=pending while running, status=completed with the full array of KYC results once done, status=failed on error, or status=not_found if the job_id is unknown or expired (TTL 24h). Call this after the eta_seconds hint returned by kyc_screene...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/kyc-screener-batch-result.md
What kyc_screener_batch_result does on Gapup Mcp
AI agents call kyc_screener_batch_result to retrieve information from Gapup Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job_id returned by kyc_screener_batch (prefix: kycb_) |
Parameters from the server's own tool schema.
Why kyc_screener_batch_result is rated Low
This tool only retrieves/polls the result of a previously submitted KYC batch job. It performs no writes, executions, or financial actions — purely reading back status and results. Severity is medium because KYC data is sensitive PII/compliance data that could be misused if exposed.
From the tool's definition Poll the result of a kyc_screener_batch job. Returns status=pending while running, status=completed with the full array of KYC results once done
Attacks that exploit this kind of access
The rule that runs kyc_screener_batch_result safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kyc_screener_batch_result, this is the rule to start with:
kyc_screener_batch_result 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 Gapup Mcp, apply this rule, and every kyc_screener_batch_result call is checked against it from then on.
Questions about kyc_screener_batch_result
Poll the result of a kyc_screener_batch job. Returns status=pending while running, status=completed with the full array of KYC results once done, status=failed on error, or status=not_found if the job_id is unknown or expired (TTL 24h). Call this after the eta_seconds hint returned by kyc_screener_batch. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
kyc_screener_batch_result accepts 1 parameter: job_id. Required: job_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for kyc_screener_batch_result: 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 Gapup Mcp. Nothing to install.
kyc_screener_batch_result 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 kyc_screener_batch_result 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 kyc_screener_batch_result. 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.
kyc_screener_batch_result is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue