Get the final result text from a completed Tendem task.
AI agents call get_task_result to retrieve information from Tendem MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the result of an already-completed task. It performs a read-only query operation with no ability to modify, delete, or execute actions. The blast radius is minimal—the tool can only expose task result data that already exists. It is lower risk than related tools like create_task or approve_task which modify task state.
From the tool's definition Tool name 'get_task_result' and description 'Get the final result text from a completed Tendem task' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the final result text from a completed Tendem task. It is categorised as a Read tool in the Tendem MCP MCP Server, which means it retrieves data without modifying state.
Register the Tendem 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 Tendem MCP. 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 Tendem MCP server (toloka/tendem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.