Poll the status and result of a previously submitted OSINT task.
AI agents call get_task_result to retrieve information from MCP OSINT Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status and results of existing tasks without creating, modifying, deleting, or executing anything. It is a passive query mechanism. The OSINT server operates in a sandboxed environment, and polling task results poses minimal risk even in adversarial scenarios—it cannot be weaponized to cause harm beyond information disclosure of results the agent already knows were computed.
From the tool's definition Tool description states it 'Poll[s] the status and result of a previously submitted OSINT task' — a pure retrieval operation with no side effects or modifications to data.
Attacks that exploit this kind of access
Poll the status and result of a previously submitted OSINT task. It is categorised as a Read tool in the MCP OSINT Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OSINT Server MCP server in PolicyLayer and add a rule for get_task_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 MCP OSINT Server. Nothing to install.
get_task_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 get_task_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 get_task_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.
get_task_result is provided by the MCP OSINT Server MCP server (lliwi/osint-mcp). 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 →