Low Risk

getTaskById

Get a specific task by ID from Teamwork

How to control getTaskById ↓

What getTaskById does on Teamwork MCP

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

Low Risk

Why getTaskById needs a policy

This tool queries and retrieves task data by ID without modifying, deleting, executing code, or performing financial transactions. It is a straightforward read operation typical of data retrieval APIs.

From the tool's definition Tool name 'getTaskById' and description 'Get a specific task by ID from Teamwork' indicate a retrieval operation with no side effects.

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

How to control getTaskById

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 getTaskById:

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

getTaskById 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 Teamwork MCP — 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.

Related tools and policies

Go deeper

Questions about getTaskById

What does the getTaskById tool do? +

Get a specific task by ID from 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 getTaskById? +

Register the Teamwork MCP server in PolicyLayer and add a rule for getTaskById: 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 getTaskById? +

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

Can I rate-limit getTaskById? +

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

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

getTaskById 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.

Free to start. No card required.

36 Teamwork MCP tools catalogued and risk-classified — across an index of 43,000+ 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.