Get information about active (running) tasks.
AI agents call get_active_tasks to retrieve information from Celery MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring data about currently executing tasks in a Celery queue. It performs a read-only lookup operation—analogous to 'list' or 'get'—returning status information without modifying, executing, or deleting any tasks. The only potential risk is information disclosure if sensitive task details are exposed, but this is low-severity compared to execution or destructive operations.
From the tool's definition Tool name 'get_active_tasks' and description 'Get information about active (running) tasks' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get information about active (running) tasks. It is categorised as a Read tool in the Celery MCP MCP Server, which means it retrieves data without modifying state.
Register the Celery MCP server in PolicyLayer and add a rule for get_active_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 Celery MCP. Nothing to install.
get_active_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 get_active_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 get_active_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.
get_active_tasks is provided by the Celery MCP server (joeyrubas/celery-mcp). 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 →