This record as markdown: /tools/onesi-genesis-mcp/scopes-listtasks.md
What scopes_listTasks does on Genesis
AI agents call scopes_listTasks to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
open | boolean | — | Only tasks that are not done or canceled |
after | integer | — | Return items after this cursor (default 0) |
label | string | — | |
limit | integer | — | Page size, 1-200 (default 50) |
status | string | — | One status, or several separated by commas (`todo,in_progress`) |
assignee | string | — | Assignee `ref` or principal |
parent_id | string | — | |
project_id | string | — | |
include_archived | boolean | — |
Parameters from the server's own tool schema.
Why scopes_listTasks is rated Low
Even though scopes_listTasks only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs scopes_listTasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scopes_listTasks, this is the rule to start with:
scopes_listTasks 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 Genesis, apply this rule, and every scopes_listTasks call is checked against it from then on.
Questions about scopes_listTasks
List tasks (GET /v1/scopes/tasks). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
scopes_listTasks accepts 9 parameters: open, after, label, limit, status, assignee, parent_id, project_id, include_archived. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for scopes_listTasks: 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 Genesis. Nothing to install.
scopes_listTasks 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 scopes_listTasks 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 scopes_listTasks. 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.
scopes_listTasks is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue