servers_bootstrap_proxy
Run servers.bootstrap-proxy through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/servers-bootstrap-proxy.md
What servers_bootstrap_proxy does on Appaloft
AI agents invoke servers_bootstrap_proxy to trigger actions in Appaloft. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | |
serverId | string | Yes | |
attemptId | string | — | |
edgeProxyProviderKey | string | — |
Parameters from the server's own tool schema.
Why servers_bootstrap_proxy is rated High
This tool executes a bootstrap proxy operation on servers, which is an Execute-category action—it triggers an external operation whose effects depend on arguments and configuration. While not inherently destructive, bootstrapping can reconfigure or reinitialize systems, making misuse a high-severity risk. The mechanism is shared with CLI and HTTP/API, broadening potential attack surface.
From the tool's definition Tool name 'servers_bootstrap_proxy' and description stating it 'Run[s] servers.bootstrap-proxy through the Appaloft application operation catalog' indicates execution of a server bootstrap operation.
Attacks that exploit this kind of access
The rule that runs servers_bootstrap_proxy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For servers_bootstrap_proxy, this is the rule to start with:
servers_bootstrap_proxy 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 Appaloft, apply this rule, and every servers_bootstrap_proxy call is checked against it from then on.
Questions about servers_bootstrap_proxy
Run servers.bootstrap-proxy through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
servers_bootstrap_proxy accepts 4 parameters: reason, serverId, attemptId, edgeProxyProviderKey. Required: serverId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for servers_bootstrap_proxy: 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 Appaloft. Nothing to install.
servers_bootstrap_proxy 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 servers_bootstrap_proxy 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 servers_bootstrap_proxy. 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.
servers_bootstrap_proxy is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue