foundry_start_empty_project
Starts a blank project for collaborative workspace
This record as markdown: /tools/nitrostack/foundry-start-empty-project.md
What foundry_start_empty_project does on Nitrostack
AI agents invoke foundry_start_empty_project to trigger actions in Nitrostack. 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 foundry_start_empty_project is rated High
Initiates project creation with external effects; outcome depends on system state and configuration.
From the tool's definition Starts a blank project for collaborative workspace
Attacks that exploit this kind of access
The rule that runs foundry_start_empty_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For foundry_start_empty_project, this is the rule to start with:
foundry_start_empty_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every foundry_start_empty_project call is checked against it from then on.
Questions about foundry_start_empty_project
Starts a blank project for collaborative workspace. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nitrostack MCP server in PolicyLayer and add a rule for foundry_start_empty_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 Nitrostack. Nothing to install.
foundry_start_empty_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the foundry_start_empty_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.
Set action: deny in the PolicyLayer policy for foundry_start_empty_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.
foundry_start_empty_project is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue