dependency_resources_import
Run dependency-resources.import through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/dependency-resources-import.md
What dependency_resources_import does on Appaloft
AI agents invoke dependency_resources_import 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 | |
projectId | string | Yes | |
secretRef | string | — | |
description | string | — | |
capabilities | array | — | |
connectionUrl | string | Yes | |
environmentId | string | Yes | |
connectionSecret | string | — | |
backupRelationship | object | — |
Parameters from the server's own tool schema.
Why dependency_resources_import is rated High
The tool 'runs' an operation called 'dependency-resources.import', which implies executing an import process that likely creates or modifies dependency resources within the application. The word 'Run' indicates execution of an operation rather than a simple read or write. Import operations can have broad side effects (creating/modifying multiple resources), justifying a high severity.
From the tool's definition 'Run dependency-resources.import through the Appaloft application operation catalog'
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs dependency_resources_import 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_import, this is the rule to start with:
dependency_resources_import 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_import call is checked against it from then on.
Questions about dependency_resources_import
Run dependency-resources.import 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_import accepts 10 parameters: kind, name, projectId, secretRef, description, capabilities, connectionUrl, environmentId, connectionSecret, backupRelationship. Required: kind, name, projectId, connectionUrl, 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_import: 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_import 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_import 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_import. 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_import 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