request_user_input · Interactive MCP: Risk & Policy

WHAT IT DOES

What request_user_input does on Interactive

AI agents invoke request_user_input to trigger actions in Interactive. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why request_user_input needs a policy

request_user_input triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

request_user_input Rate-limited

request_user_input stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Interactive, so you can run agents against it safely.

FAQ

Questions about request_user_input

What does the request_user_input tool do? +

request_user_input. It is categorised as a Execute tool in the Interactive MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on request_user_input? +

Register the Interactive 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 Interactive. Nothing to install.

What risk level is request_user_input? +

request_user_input is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 Interactive MCP server (mikeysrecipes/interactive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.