This record as markdown: /tools/nasbridge/initshutdown-create.md
What initshutdown_create does on Nasbridge
AI agents use initshutdown_create to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why initshutdown_create is rated Medium
Creates a new init/shutdown script that will execute during system startup or shutdown. While this is a write operation (creating a new record), the created script can execute arbitrary code at system boot/shutdown, making misuse potentially high-impact. However, the act of creating the script itself is a Write operation — execution happens separately when the system boots/shuts down.
From the tool's definition Create an init/shutdown script
Attacks that exploit this kind of access
The rule that runs initshutdown_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For initshutdown_create, this is the rule to start with:
initshutdown_create 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 Nasbridge, apply this rule, and every initshutdown_create call is checked against it from then on.
Questions about initshutdown_create
Create an init/shutdown script. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for initshutdown_create: 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 Nasbridge. Nothing to install.
initshutdown_create 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 initshutdown_create 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 initshutdown_create. 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.
initshutdown_create is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue