// MCP TOOL REFERENCE

DEV WORKFLOW MCP SERVER TOOLS

17 tools from the Dev Workflow MCP Server MCP Server, categorised by risk level.

View the Dev Workflow MCP Server policy →

// ALL 17 DEV WORKFLOW MCP SERVER TOOLS

READ 4 tools

Read check_ready_to_commit Verify all steps are complete Read continue_workflow Get next-step guidance Read get_workflow_status Show current status Read view_history View completed tasks

WRITE 7 tools

Write commit_and_push Commit and push changes Write complete_task Mark task as complete and reset Write create_documentation Mark documentation as created Write create_tests Mark that tests have been created Write mark_bug_fixed Mark the feature/bug as fixed (requires tests next) Write perform_release Record release details (or use `skip_release` when the project has no release automation) Write skip_tests Skip tests with justification

DESTRUCTIVE 3 tools

Destructive drop_task Abandon current task Destructive force_complete_task Force completion with reason Destructive rerun_workflow Reset and restart the current task from the beginning

EXECUTE 3 tools

Execute run_full_workflow Execute every workflow step in sequence with a single command (requires supplying the details for each phase) Execute run_tests Record test results (must pass to proceed) Execute start_task Begin a new coding task

// RUNNING THIS SERVER

The managed route: connect Dev Workflow MCP Server through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @programinglive/dev-workflow-mcp-server

// FAQ

How many tools does the Dev Workflow MCP Server MCP server have? +

The Dev Workflow MCP Server MCP server exposes 17 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Dev Workflow MCP Server tools? +

Route the Dev Workflow MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Dev Workflow MCP Server tools fall into? +

Dev Workflow MCP Server tools are categorised as Read (4), Write (7), Destructive (3), Execute (3). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.