Check the status and progress of a background task by its unique ID.
AI agents call get_task_status to retrieve information from Prospectio MCP API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing background task. It queries state without modifying, deleting, or executing any operations. The blast radius if misused is minimal—an agent could at worst retrieve status information it shouldn't access, but cannot cause harm through this tool alone. This is a straightforward Read operation.
From the tool's definition Tool name 'get_task_status' and description 'Check the status and progress of a background task by its unique ID' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_task_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prospectio MCP API, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_task_status": {}
}
} get_task_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status and progress of a background task by its unique ID. It is categorised as a Read tool in the Prospectio MCP API MCP Server, which means it retrieves data without modifying state.
Register the Prospectio MCP API MCP server in PolicyLayer and add a rule for get_task_status: 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 Prospectio MCP API. Nothing to install.
get_task_status 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 get_task_status 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 get_task_status. 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.
get_task_status is provided by the Prospectio MCP API MCP server (prospectio-ai/prospectio-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prospectio MCP API, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Prospectio MCP API tools catalogued and risk-classified — across an index of 43,000+ MCP servers.