mark_task_waiting_for_user

THE RISK

Low Risk

Why mark_task_waiting_for_user needs a policy

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.

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

POLICY

How to control mark_task_waiting_for_user

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

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"
        }
      ]
    }
  }
}

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

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

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Allcanuse tools

Destructive cancel_background_task cancel_background_task Destructive delete_path delete_path Destructive kill_process kill_process Execute compile_c_program compile_c_program Execute deploy_and_update_service deploy_and_update_service Execute run_cmd run_cmd Execute run_powershell run_powershell Execute run_shell run_shell

All 130 Allcanuse tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mark_task_waiting_for_user

What does the mark_task_waiting_for_user tool do? +

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

Enforce policy on every Allcanuse tool call.

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

CHECK YOUR STACK →