mark_task_waiting_for_user

A other tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/mark-task-waiting-for-user.md

WHAT IT DOES

What mark_task_waiting_for_user does on Allcanuse

AI agents call mark_task_waiting_for_user as a supporting operation in Allcanuse workflows.

RISK

Why mark_task_waiting_for_user is rated Low

The tool name suggests it updates a task status to indicate it is waiting for user input, which would be a Write operation. However, with no description available, the exact behavior is uncertain. Based on the name alone, this appears to be a minor state/status update with low blast radius. Confidence is reduced due to empty description.

From the tool's definition Tool name is 'mark_task_waiting_for_user'; description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mark_task_waiting_for_user safely

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

mark_task_waiting_for_user Rate-limited

mark_task_waiting_for_user gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_task_waiting_for_user": {
      "limits": [
        {
          "counter": "mark_task_waiting_for_user_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mark_task_waiting_for_user

What does the mark_task_waiting_for_user tool do? +

mark_task_waiting_for_user is a other tool on the Allcanuse MCP server. It is categorised as a Other tool in the Allcanuse MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on mark_task_waiting_for_user? +

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

What risk level is mark_task_waiting_for_user? +

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

Can I rate-limit mark_task_waiting_for_user? +

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

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

mark_task_waiting_for_user is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

my_task on Agent Jail → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →