list_agent_tasks
The standing tasks an instance carries in its own task store — the ones injected into its system prompt every turn, NOT the runtime board (for that use instance_board or get_instance_task). Returns each task with
This record as markdown: /tools/io-github-proagentstore-platform/list-agent-tasks.md
What list_agent_tasks does on ProAgentStore
AI agents call list_agent_tasks to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_agent_tasks is rated Low
Retrieves task metadata from storage without modifying data or triggering actions.
From the tool's definition list standing tasks instance carries task store returns each task
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_agent_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_agent_tasks, this is the rule to start with:
list_agent_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 ProAgentStore, apply this rule, and every list_agent_tasks call is checked against it from then on.
Questions about list_agent_tasks
The standing tasks an instance carries in its own task store — the ones injected into its system prompt every turn, NOT the runtime board (for that use instance_board or get_instance_task). Returns each task with. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for list_agent_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 ProAgentStore. Nothing to install.
list_agent_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_agent_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_agent_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_agent_tasks is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue