list_tasks
AI agents call list_tasks to retrieve information from Tianshu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to list existing tasks without modifying, executing, or destroying anything. The naming convention aligns with read-only query operations typical in a document processing pipeline. The empty description and reliance on contextual inference lowers confidence slightly from maximum, but the 'list' verb and sibling tool patterns provide reasonable justification for Read classification.
From the tool's definition Tool name 'list_tasks' indicates retrieval of task information. The empty description prevents direct confirmation, but the name pattern and context (sibling tools include 'get_queue_stats' and 'get_task_status', which are clearly read operations) strongly…
Attacks that exploit this kind of access
list_tasks. It is categorised as a Read tool in the Tianshu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tianshu MCP Server 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 Tianshu MCP Server. 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 Tianshu MCP Server MCP server (magicyuan876/mineru-tianshu). 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 →