AI agents call get_task_status to retrieve information from Outx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only utility function used to check the status of asynchronous operations initiated by other LinkedIn API tools. It retrieves status information without creating, modifying, deleting, or executing any actions. The incomplete description suggests it is a polling/recovery mechanism for tasks initiated elsewhere, making it a simple informational read operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_task_status' and description 'Recovery tool' that 'polls automatically' and 'returns the result directly' indicates a status-checking/polling operation with no data modification capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Recovery tool. Every other LinkedIn Data API tool polls automatically for ~150 seconds and returns the result directly, so you almost never need this. Use it ONLY when another tool returns a. It is categorised as a Read tool in the Outx MCP Server, which means it retrieves data without modifying state.
Register the Outx 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 Outx. 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 Outx MCP server (outx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →