get_task
AI agents call get_task 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.
The naming convention and context from related tools (list_tasks, get_task_result) strongly suggests this is a read-only operation that retrieves task information. No description is available, which slightly reduces confidence, but the pattern of sibling tools and the 'get_' prefix are reliable indicators of query/retrieval semantics with no side effects.
From the tool's definition Tool name 'get_task' with no description provided. Based on sibling tools on the same server (list_tasks, get_task_result, get_all_task_results), this appears to be a retrieval operation that queries task information without modifying state.
Attacks that exploit this kind of access
get_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: 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 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 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. 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 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.