user_input_required_guidance

THE RISK

Low Risk

Why user_input_required_guidance needs a policy

This tool provides guidance/workflow orchestration for escalating to user input at checkpoints or iteration limits. It doesn't read data, write/modify data, execute code, destroy data, or move money. It's a workflow control mechanism that prompts for human intervention, fitting 'Other' as it manages process flow rather than performing data operations.

From the tool's definition Handle escalation to user input when iteration limits reached or checkpoints triggered

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

POLICY

How to control user_input_required_guidance

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

policy.json

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

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

Create a free account and register Structured Workflow MCP — 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 Structured Workflow MCP tools

Execute build_custom_workflow Build a custom workflow with full control over phases and configuration. Use specific work Execute refactor_workflow Start a structured refactoring workflow to improve existing code without changing function Execute tdd_workflow Start a Test-Driven Development workflow with Red-Green-Refactor cycles Execute test_guidance Get MANDATORY guidance for the TEST phase - execute tests and validate functionality after Write phase_output Record the output/results when completing a workflow phase - REQUIRES ACTUAL OUTPUT ARTIFA Write test_workflow Start a focused workflow for writing or improving test coverage Write create_feature_workflow Start a structured workflow for adding new functionality with integrated testing Read audit_inventory_guidance Get guidance for the AUDIT_INVENTORY phase - analyze code and catalog changes

All 20 Structured Workflow MCP 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 user_input_required_guidance

What does the user_input_required_guidance tool do? +

Handle escalation to user input when iteration limits reached or checkpoints triggered. It is categorised as a Other tool in the Structured Workflow MCP MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on user_input_required_guidance? +

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

What risk level is user_input_required_guidance? +

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

Can I rate-limit user_input_required_guidance? +

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

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

user_input_required_guidance is provided by the Structured Workflow MCP server (kingdomseed/structured-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Structured Workflow MCP tool call.

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

CHECK YOUR STACK →