resources_bind_dependency
Run resources.bind-dependency through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-bind-dependency.md
What resources_bind_dependency does on Appaloft
AI agents invoke resources_bind_dependency 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 |
|---|---|---|---|
scope | string | — | |
resourceId | string | Yes | |
targetName | string | Yes | |
injectionMode | string | — | |
dependencyResourceId | string | Yes |
Parameters from the server's own tool schema.
Why resources_bind_dependency is rated High
This tool executes an application operation ('run') rather than simply reading data. Binding dependencies typically creates or alters system configurations and inter-component relationships. While not explicitly destructive or irreversible in the description, it performs an active operation that modifies system state.
From the tool's definition Tool name 'resources_bind_dependency' combined with description stating it 'Run[s] resources.bind-dependency through the Appaloft application operation catalog' indicates execution of an application operation.
Attacks that exploit this kind of access
The rule that runs resources_bind_dependency 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 resources_bind_dependency, this is the rule to start with:
resources_bind_dependency 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 resources_bind_dependency call is checked against it from then on.
Questions about resources_bind_dependency
Run resources.bind-dependency 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.
resources_bind_dependency accepts 5 parameters: scope, resourceId, targetName, injectionMode, dependencyResourceId. Required: resourceId, targetName, dependencyResourceId. 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 resources_bind_dependency: 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.
resources_bind_dependency 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 resources_bind_dependency 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 resources_bind_dependency. 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.
resources_bind_dependency 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