getTaskSubtasks

THE RISK

Low Risk

Why getTaskSubtasks needs a policy

This tool retrieves subtask data for a given task. It performs a read-only query against the Teamwork API with no ability to create, modify, or delete data. The blast radius of misuse is minimal—an AI agent could over-query or access subtasks it shouldn't, but cannot alter project state.

From the tool's definition Tool name 'getTaskSubtasks' and description 'Get all subtasks for a specific task in Teamwork' indicate a query/retrieval operation with no modification or side effects.

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

POLICY

How to control getTaskSubtasks

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

policy.json

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

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

Create a free account and register Teamwork MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Teamwork MCP tools

Destructive deleteCompany This tool allows you to delete a company, be careful with this tool as it will delete the Destructive deletePerson Delete a person from Teamwork Destructive deleteTask Delete a task from Teamwork Write addPeopleToProject Add people to a specific project in Teamwork Write createComment Creates a new comment for a specific resource (tasks, milestones, notebooks, links, fileve Write createCompany Create a new company. This tool allows you to create a company. The request requires a com Write createProject Create a new project in Teamwork Write createSubTask Creates a subtask. Create a new subtask under the provided parent task.

All 36 Teamwork MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getTaskSubtasks

What does the getTaskSubtasks tool do? +

Get all subtasks for a specific task in Teamwork. It is categorised as a Read tool in the Teamwork MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTaskSubtasks? +

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

What risk level is getTaskSubtasks? +

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

Can I rate-limit getTaskSubtasks? +

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

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

getTaskSubtasks is provided by the Teamwork MCP server (vizioz/teamwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Teamwork MCP tool call.

Start from Teamwork MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →