util_rename_key

Rename a single object key

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-rename-key.md

WHAT IT DOES

What util_rename_key does on Delx Protocol — Agent Recovery & Continuity

AI agents use util_rename_key to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.

Parameter	Type	Required	Description
`object`	object	Yes	Input field: object.
`to_key`	string	Yes	Input field: to key.
`from_key`	string	Yes	Input field: from key.

Parameters from the server's own tool schema.

RISK

Why util_rename_key is rated Medium

An AI agent can call util_rename_key faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_rename_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_rename_key, this is the rule to start with:

util_rename_key Rate-limited

util_rename_key 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": {
    "util_rename_key": {
      "limits": [
        {
          "counter": "util_rename_key_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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_rename_key call is checked against it from then on.

FAQ

Questions about util_rename_key

What does the util_rename_key tool do? +

Rename a single object key. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does util_rename_key accept? +

util_rename_key accepts 3 parameters: object, to_key, from_key. Required: object, to_key, from_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_rename_key? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_rename_key: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.

What risk level is util_rename_key? +

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

Can I rate-limit util_rename_key? +

Yes. Add a rate_limit block to the util_rename_key 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 util_rename_key completely? +

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

util_rename_key is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.

This server

All 1076 Delx Protocol — Agent Recovery & Continuity tools →

Across the catalogue

The MCP Attack Database →

Guides

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