orchestrate_new_project

THE RISK

High Risk

Why orchestrate_new_project needs a policy

This tool performs orchestration—coordinating and executing multiple setup steps (template application, file creation, configuration deployment) across potentially multiple systems. The capability to 'orchestrate setup' of a complete project means executing commands, creating resources, and potentially interacting with external systems (AWS, development environments).

From the tool's definition Tool name 'orchestrate_new_project' combined with description 'Orchestrate the setup of a new software project' indicates automated execution of project initialization workflows.

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

POLICY

How to control orchestrate_new_project

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "orchestrate_new_project": {
      "limits": [
        {
          "counter": "orchestrate_new_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register MCP Project Orchestrator — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Project Orchestrator tools

Write deploy_skills_to_cursor Deploy Agent Skills as Cursor configuration. Write apply_project_template Apply a template and create comprehensive documentation. Write create_project_with_skills Create project using Agent Skills orchestration. Read analyze_design_patterns Analyze the user's idea to identify design patterns and architecture concepts. Read aws_best_practices Get AWS best practices for a specific service (s3, ec2, lambda) Read aws_estimate_costs Estimate AWS costs based on usage (JSON format) Read aws_list_ec2_instances List all EC2 instances in the current region Read aws_list_lambda_functions List all Lambda functions in the current region

All 15 MCP Project Orchestrator tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MCP Project Orchestrator → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about orchestrate_new_project

What does the orchestrate_new_project tool do? +

Orchestrate the setup of a new software project from the user's idea. It is categorised as a Execute tool in the MCP Project Orchestrator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on orchestrate_new_project? +

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

What risk level is orchestrate_new_project? +

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

Can I rate-limit orchestrate_new_project? +

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

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

orchestrate_new_project is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Project Orchestrator tool call.

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

CHECK YOUR STACK →