list_active_tasks
A read tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/list-active-tasks.md
What list_active_tasks does on Pengstrike
AI agents call list_active_tasks to retrieve information from Pengstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_active_tasks is rated Low
This tool retrieves and lists active tasks without modifying, deleting, or executing any operations. It has no side effects and poses minimal risk. The absence of a description does not significantly lower confidence because the name is explicitly descriptive of a read operation and is consistent with the server's stated capability to 'list tasks'.
From the tool's definition Tool name 'list_active_tasks' indicates a retrieval operation that queries tasks from Todoist. Server description confirms it 'enables AI agents to create and list tasks' with 'project-based filtering', establishing this as a read-only query.
Attacks that exploit this kind of access
The rule that runs list_active_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_active_tasks, this is the rule to start with:
list_active_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 Pengstrike, apply this rule, and every list_active_tasks call is checked against it from then on.
Questions about list_active_tasks
list_active_tasks is a read tool on the Pengstrike MCP server. It is categorised as a Read tool in the Pengstrike MCP Server, which means it retrieves data without modifying state.
Register the Pengstrike MCP server in PolicyLayer and add a rule for list_active_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 Pengstrike. Nothing to install.
list_active_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_active_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_active_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_active_tasks is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
This server
Across the catalogue