dependency_resources_rename

Run dependency-resources.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/dependency-resources-rename.md

WHAT IT DOES

What dependency_resources_rename does on Appaloft

AI agents use dependency_resources_rename to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.

Parameter	Type	Required	Description
`name`	string	Yes
`dependencyResourceId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why dependency_resources_rename is rated Medium

Renaming resources is a reversible modification operation (Write category). The high severity reflects that renaming dependency resources could break references, affect deployments, or impact system consistency if misapplied by an AI agent without proper validation.

From the tool's definition Tool name contains 'rename' which modifies resource metadata; description indicates it 'Run[s]' an operation through the Appaloft application catalog, suggesting a state-changing action rather than read-only or destructive deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dependency_resources_rename 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_rename, this is the rule to start with:

dependency_resources_rename Rate-limited

dependency_resources_rename stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dependency_resources_rename": {
      "limits": [
        {
          "counter": "dependency_resources_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every dependency_resources_rename call is checked against it from then on.

FAQ

Questions about dependency_resources_rename

What does the dependency_resources_rename tool do? +

Run dependency-resources.rename through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does dependency_resources_rename accept? +

dependency_resources_rename accepts 2 parameters: name, dependencyResourceId. Required: name, dependencyResourceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dependency_resources_rename? +

Register the Appaloft MCP server in PolicyLayer and add a rule for dependency_resources_rename: 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.

What risk level is dependency_resources_rename? +

dependency_resources_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dependency_resources_rename? +

Yes. Add a rate_limit block to the dependency_resources_rename 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.

How do I block dependency_resources_rename completely? +

Set action: deny in the PolicyLayer policy for dependency_resources_rename. 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.

What MCP server provides dependency_resources_rename? +

dependency_resources_rename 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.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →