checkOperationStatus
checkOperationStatus: poll an async operation and retrieve its results or CSV download URL. Use this after any tool call made with responseType="paging" or responseType="csv" — those return an operationId that must be polled via checkOperationStatus to get the actual data. Also handles background...
This record as markdown: /tools/ai-xpoz-social-insights/checkoperationstatus.md
What checkOperationStatus does on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)
AI agents call checkOperationStatus to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) 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 |
|---|---|---|---|
feedback | string | — | Optional. Any free-form feedback you want to share — about this tool, other tools, the platform overall, or anything else. Feedback does NOT have to be about th |
_requestId | string | — | |
operationId | string | Yes | The operation ID |
Parameters from the server's own tool schema.
Why checkOperationStatus is rated Low
This tool exclusively queries and retrieves data from previously initiated operations. It performs no side effects, modifications, or destructive actions. The worst-case misuse (spam polling, resource exhaustion) poses minimal blast radius compared to other tools on this server. Classified as Read with low severity.
From the tool's definition checkOperationStatus polls an async operation and retrieves its results or CSV download URL; returns paginated results, dataDumpExportOperationId, and presigned S3 links. No creation, modification, deletion, execution, or financial operations occur.
Attacks that exploit this kind of access
The rule that runs checkOperationStatus safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For checkOperationStatus, this is the rule to start with:
checkOperationStatus 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), apply this rule, and every checkOperationStatus call is checked against it from then on.
Questions about checkOperationStatus
checkOperationStatus: poll an async operation and retrieve its results or CSV download URL. Use this after any tool call made with responseType="paging" or responseType="csv" — those return an operationId that must be polled via checkOperationStatus to get the actual data. Also handles background job status checks, presigned S3 link retrieval for data dumps, and completion polling for long-running queries. Required: operationId. HANDLES TWO TYPES: (1) Query operations (op_toolname_xxx): returns paginated results + dataDumpExportOperationId. (2) Export operations (op_datadump_xxx): returns download URL for CSV download. CRITICAL: You MUST keep polling until operation finishes. DO NOT stop until status is success/no_data/error/cancelled. POLLING LOOP: (1) Call immediately after getting operation ID. (2) If status=running, wait exactly 5 seconds. (3) Call again after 5 seconds. (4) Repeat step 2-3 continuously until status changes to success/no_data/error/cancelled. (5) Only stop when operation is finished. NOTE: status values returned are wire-level ResponseStatus (success/no_data/error/running/cancelled). Returns: For queries - results, pagination, dataDumpExportOperationId. For exports - downloadUrl, fileName, totalRows. NEVER make calls without 5 second waits between them. MIGRATION NOTE: checkOperationStatus was renamed from checkDataDumpOperationStatus and getOperationResults — if you were calling those tool names, use this one instead. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.
checkOperationStatus accepts 3 parameters: feedback, _requestId, operationId. Required: operationId. The full parameter table on this page comes from the server's own tool schema.
Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for checkOperationStatus: 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.
checkOperationStatus 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 checkOperationStatus 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 checkOperationStatus. 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.
checkOperationStatus is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and thousands of servers like it.
Across the catalogue