list_background_tasks

A read tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/list-background-tasks.md

WHAT IT DOES

What list_background_tasks does on Allcanuse

AI agents call list_background_tasks to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_background_tasks is rated Low

The tool queries the state of running background tasks on the system. While querying system state could inform privilege escalation or reconnaissance, listing background tasks is fundamentally a read operation with no direct side effects—it retrieves information without creating, modifying, or deleting data.

From the tool's definition Tool name 'list_background_tasks' indicates retrieval/enumeration of background tasks without modification. The empty description limits certainty, but the 'list' operation pattern is universally associated with read-only queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_background_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_background_tasks, this is the rule to start with:

list_background_tasks Allowed

list_background_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_background_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every list_background_tasks call is checked against it from then on.

FAQ

Questions about list_background_tasks

What does the list_background_tasks tool do? +

list_background_tasks is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_background_tasks? +

Register the Allcanuse 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 Allcanuse. Nothing to install.

What risk level is list_background_tasks? +

list_background_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_background_tasks? +

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.

How do I block list_background_tasks completely? +

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.

What MCP server provides list_background_tasks? +

list_background_tasks is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

list_tasks on 0rca Dojo MCP Server →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →