list_tasks
List tasks in the marketplace. Optionally filter by type or status.
This record as markdown: /tools/network-tenzro-tenzro/list-tasks.md
What list_tasks does on Tenzro Ledger MCP
AI agents call list_tasks to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_tasks is rated Low
The tool retrieves and filters existing task data from the marketplace without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with minimal security risk.
From the tool's definition Tool name is 'list_tasks' and description states it 'List tasks in the marketplace. Optionally filter by type or status.' This is a read operation that retrieves/queries data with no side effects.
Attacks that exploit this kind of access
The rule that runs list_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_tasks, this is the rule to start with:
list_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every list_tasks call is checked against it from then on.
Questions about list_tasks
List tasks in the marketplace. Optionally filter by type or status. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger 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 Tenzro Ledger 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 Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue