List all Tendem tasks with their statuses.
AI agents call list_tasks 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 only queries and returns information about existing tasks. It has no side effects, does not execute code, does not modify data, and does not commit financial or destructive operations. It is a straightforward data retrieval operation consistent with the Read category.
From the tool's definition Tool name is 'list_tasks' and description states it 'List all Tendem tasks with their statuses' — a pure retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
List all Tendem tasks with their statuses. 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 list_tasks: 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.
list_tasks 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 list_tasks 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 list_tasks. 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.
list_tasks 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.