sandboxes_network_policy_configure
Run sandboxes.network-policy.configure through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-network-policy-configure.md
What sandboxes_network_policy_configure does on Appaloft
AI agents invoke sandboxes_network_policy_configure 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 |
|---|---|---|---|
sandboxId | string | Yes | |
networkPolicy | object | Yes |
Parameters from the server's own tool schema.
Why sandboxes_network_policy_configure is rated High
The tool 'runs' an operation to configure network policy for sandboxes, which triggers an external operation with potentially significant security implications (controlling network access rules). 'Configure' implies modifying system-level settings, but the description frames it as 'running' an operation through a catalog, making Execute the most appropriate category.
From the tool's definition 'Run sandboxes.network-policy.configure through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs sandboxes_network_policy_configure 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 sandboxes_network_policy_configure, this is the rule to start with:
sandboxes_network_policy_configure 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 sandboxes_network_policy_configure call is checked against it from then on.
Questions about sandboxes_network_policy_configure
Run sandboxes.network-policy.configure 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.
sandboxes_network_policy_configure accepts 2 parameters: sandboxId, networkPolicy. Required: sandboxId, networkPolicy. 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 sandboxes_network_policy_configure: 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.
sandboxes_network_policy_configure 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 sandboxes_network_policy_configure 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 sandboxes_network_policy_configure. 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.
sandboxes_network_policy_configure 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