Check the status of a previously posted task. Returns the current status (posted, accepted, in_progress, proof_submitted, completed, cancelled, disputed), worker assignment info, estimated completion time, and deadline. If the task is completed, includes the worker's deliverable, worker rating, t...
Part of the Reversecentaur server.
Free to start. No card required.
AI agents call check_task to retrieve information from Reversecentaur without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_task only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"check_task": {}
}
}See the full Reversecentaur policy for all 6 tools.
These attack patterns abuse exactly the kind of access check_task gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check the status of a previously posted task. Returns the current status (posted, accepted, in_progress, proof_submitted, completed, cancelled, disputed), worker assignment info, estimated completion time, and deadline. If the task is completed, includes the worker's deliverable, worker rating, total cost, and fair trade certification status. Poll this after posting a task to track progress.. It is categorised as a Read tool in the Reversecentaur MCP Server, which means it retrieves data without modifying state.
Register the Reversecentaur MCP server in PolicyLayer and add a rule for check_task: 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 Reversecentaur. Nothing to install.
check_task 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 check_task 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 check_task. 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.
check_task is provided by the Reversecentaur MCP server (reversecentaur-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Reversecentaur tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.