setup_demo
Quick setup: Register all 3 demo mock servers (filesystem, CRM, email) with the gateway in one step. Useful for demo initialization.
This record as markdown: /tools/nitrostack/setup-demo.md
What setup_demo does on Nitrostack
AI agents use setup_demo to create or update resources in Nitrostack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nitrostack environment.
Why setup_demo is rated Medium
Creates and registers multiple server configurations; reversible but broad scope.
From the tool's definition Register all 3 demo mock servers with the gateway
Attacks that exploit this kind of access
The rule that runs setup_demo 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 setup_demo, this is the rule to start with:
setup_demo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every setup_demo call is checked against it from then on.
Questions about setup_demo
Quick setup: Register all 3 demo mock servers (filesystem, CRM, email) with the gateway in one step. Useful for demo initialization. It is categorised as a Write tool in the Nitrostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nitrostack MCP server in PolicyLayer and add a rule for setup_demo: 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.
setup_demo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup_demo 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 setup_demo. 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.
setup_demo 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.
This server
Across the catalogue