dependency_resources_provision
Run dependency-resources.provision through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/dependency-resources-provision.md
What dependency_resources_provision does on Appaloft
AI agents invoke dependency_resources_provision 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 |
|---|---|---|---|
kind | string | Yes | |
name | string | Yes | |
serverId | string | — | |
projectId | string | Yes | |
description | string | — | |
providerKey | string | — | |
capabilities | array | — | |
environmentId | string | Yes | |
backupRelationship | object | — |
Parameters from the server's own tool schema.
Why dependency_resources_provision is rated High
Provisioning dependencies involves running code/operations that allocate or configure external resources. This is Execute rather than Write because it executes a catalog operation whose side effects are dependent on runtime arguments and configuration, not merely creating or modifying data reversibly.
From the tool's definition Tool name 'dependency_resources_provision' and description 'Run dependency-resources.provision through the Appaloft application operation catalog' indicate execution of a provisioning operation.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs dependency_resources_provision 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 dependency_resources_provision, this is the rule to start with:
dependency_resources_provision 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 dependency_resources_provision call is checked against it from then on.
Questions about dependency_resources_provision
Run dependency-resources.provision 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.
dependency_resources_provision accepts 9 parameters: kind, name, serverId, projectId, description, providerKey, capabilities, environmentId, backupRelationship. Required: kind, name, projectId, environmentId. 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 dependency_resources_provision: 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.
dependency_resources_provision 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 dependency_resources_provision 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 dependency_resources_provision. 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.
dependency_resources_provision 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