request_user_input

Ask the user a structured multiple-choice question set and block until they respond.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/request-user-input.md

WHAT IT DOES

What request_user_input does on CoWork OS

AI agents use request_user_input to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why request_user_input is rated Medium

An AI agent can call request_user_input faster than any human can review: one bad instruction and it creates or modifies resources in CoWork OS by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs request_user_input safely

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

request_user_input Rate-limited

request_user_input stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_user_input": {
      "limits": [
        {
          "counter": "request_user_input_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about request_user_input

What does the request_user_input tool do? +

Ask the user a structured multiple-choice question set and block until they respond. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on request_user_input? +

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

What risk level is request_user_input? +

request_user_input is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit request_user_input? +

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

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

request_user_input is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →