This record as markdown: /tools/frontmcp/list-tasks.md
What list-tasks does on Frontmcp
AI agents call list-tasks to retrieve information from Frontmcp 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
This tool retrieves and displays task data without modifying, deleting, or executing actions. The verb 'list' is a classic Read category operation. Severity is low because listing tasks poses minimal risk—the blast radius of misuse is limited to information disclosure of existing task data.
From the tool's definition Tool name 'list-tasks' and description 'List all tasks' indicate a retrieval operation 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 Frontmcp, 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 Frontmcp, apply this rule, and every list-tasks call is checked against it from then on.
Questions about list-tasks
List all tasks. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front 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 Frontmcp. 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 Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue