Low Risk

list_subtasks

View subtasks, optionally filtered by task ID or project ID

How to control list_subtasks ↓

AI agents call list_subtasks to retrieve information from Agentic Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns subtask data with optional filtering parameters. It performs no modifications, deletions, or external operations. The verb 'View' and the filtering-only parameters confirm this is a read-only data retrieval operation, warranting the Read category with low severity.

From the tool's definition Tool name 'list_subtasks' and description 'View subtasks, optionally filtered by task ID or project ID' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_subtasks gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_subtasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_subtasks": {}
  }
}

list_subtasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agentic Tools MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_subtasks tool do? +

View subtasks, optionally filtered by task ID or project ID. It is categorised as a Read tool in the Agentic Tools MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_subtasks? +

Register the Agentic Tools MCP Server MCP server in PolicyLayer and add a rule for list_subtasks: 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 Agentic Tools MCP Server. Nothing to install.

What risk level is list_subtasks? +

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

Can I rate-limit list_subtasks? +

Yes. Add a rate_limit block to the list_subtasks 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_subtasks completely? +

Set action: deny in the PolicyLayer policy for list_subtasks. 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_subtasks? +

list_subtasks is provided by the Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agentic Tools MCP Server tool call.

Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.