collab_task_block

Record a blocker and release the current lease/path scopes.

SERVERAgenttool SOURCEhttps://api.agenttool.dev/v1/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-agenttool-agenttool/collab-task-block.md

WHAT IT DOES

What collab_task_block does on Agenttool

AI agents call collab_task_block to retrieve information from Agenttool without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why collab_task_block is rated Low

Even though collab_task_block only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collab_task_block safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For collab_task_block, this is the rule to start with:

collab_task_block Allowed

collab_task_block is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every collab_task_block call is checked against it from then on.

FAQ

Questions about collab_task_block

What does the collab_task_block tool do? +

Record a blocker and release the current lease/path scopes. It is categorised as a Read tool in the Agenttool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on collab_task_block? +

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

What risk level is collab_task_block? +

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

Can I rate-limit collab_task_block? +

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

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

collab_task_block is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agenttool, and thousands of servers like it.

This server

All 84 Agenttool tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →