Lists all currently running background tasks.
AI agents call list-background-tasks to retrieve information from MCP Background Task Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays data about running background tasks. It has no side effects, does not execute code, does not modify state, and does not delete anything. It is purely informational and falls squarely into the Read category.
From the tool's definition Tool name 'list-background-tasks' and description 'Lists all currently running background tasks' indicate a query operation that retrieves information about existing tasks without modifying or executing anything.
Attacks that exploit this kind of access
Lists all currently running background tasks. It is categorised as a Read tool in the MCP Background Task Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Background Task Server MCP server in PolicyLayer and add a rule for list-background-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 MCP Background Task Server. Nothing to install.
list-background-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-background-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-background-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-background-tasks is provided by the MCP Background Task Server MCP server (nanoseil/mcp-bgtask). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →