Lists issues from the task trellis system Use this tool to retrieve and filter issues based on various criteria. Essential for discovering existing work items, understanding project structure, and finding issues that need attention. Available issue types: -
AI agents call list_issues to retrieve information from Task Trellis MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation. It queries and returns issue data without creating, modifying, deleting, or executing anything. The terms 'Lists', 'retrieve', and 'discover' are characteristic of Read category tools. The blast radius if misused is minimal—an agent could only gain unauthorized visibility into issues, not cause irreversible changes or execute arbitrary operations.
From the tool's definition Tool name 'list_issues' and description explicitly states it 'Lists issues from the task trellis system' and is used to 'retrieve and filter issues'.
Documented attack patterns abuse exactly the kind of access list_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task Trellis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_issues:
{
"version": "1",
"default": "deny",
"tools": {
"list_issues": {}
}
}list_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists issues from the task trellis system Use this tool to retrieve and filter issues based on various criteria. Essential for discovering existing work items, understanding project structure, and finding issues that need attention. Available issue types: -. It is categorised as a Read tool in the Task Trellis MCP MCP Server, which means it retrieves data without modifying state.
Register the Task Trellis MCP server in PolicyLayer and add a rule for list_issues: 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 Task Trellis MCP. Nothing to install.
list_issues 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_issues 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_issues. 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_issues is provided by the Task Trellis MCP server (langadventurellc/task-trellis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Task Trellis MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Task Trellis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.