create_feature_workflow

THE RISK

Medium Risk

Why create_feature_workflow needs a policy

This tool initiates a workflow for adding new features, which constitutes creating or modifying data/code in a reversible manner. It structures the development process rather than executing arbitrary code or making destructive changes. The 'integrated testing' aspect suggests it orchestrates a series of steps but the primary action is organizing/writing new functionality.

From the tool's definition Start a structured workflow for adding new functionality with integrated testing

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

POLICY

How to control create_feature_workflow

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 create_feature_workflow:

policy.json

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

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

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.

LIMIT 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 Read audit_inventory_guidance Get guidance for the AUDIT_INVENTORY phase - analyze code and catalog changes Read compare_analyze_guidance Get guidance for the COMPARE/ANALYZE phase - evaluating approaches

All 20 Structured Workflow MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_feature_workflow

What does the create_feature_workflow tool do? +

Start a structured workflow for adding new functionality with integrated testing. It is categorised as a Write tool in the Structured Workflow MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_feature_workflow? +

Register the Structured Workflow MCP server in PolicyLayer and add a rule for create_feature_workflow: 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 create_feature_workflow? +

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

Can I rate-limit create_feature_workflow? +

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

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

create_feature_workflow 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 →