list_background_tasks
AI agents call list_background_tasks to retrieve information from Allcanuse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access list_background_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for list_background_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"list_background_tasks": {}
}
}list_background_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_background_tasks. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
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.
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 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.
Start from Allcanuse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.