rename_data_table_row
Rename a row in-place (preserves row order).
This record as markdown: /tools/aadeshrao123-unreal-mcp/rename-data-table-row.md
What rename_data_table_row does on Unreal-MCP
AI agents use rename_data_table_row to create or update resources in Unreal-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal-MCP environment.
Why rename_data_table_row is rated Medium
Renaming is a reversible modification operation that changes data without destruction. It falls under Write category rather than Destructive because the action can be undone (row can be renamed back). Severity is medium because misuse could corrupt game data organization or break references to renamed rows in an Unreal Engine project, but the effect is localized to a single row and reversible.
From the tool's definition Tool name 'rename_data_table_row' and description 'Rename a row in-place (preserves row order)' indicate modification of existing data structure metadata. The operation modifies a data table row's identifier reversibly without deletion.
Attacks that exploit this kind of access
The rule that runs rename_data_table_row safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_data_table_row, this is the rule to start with:
rename_data_table_row 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every rename_data_table_row call is checked against it from then on.
Questions about rename_data_table_row
Rename a row in-place (preserves row order). It is categorised as a Write tool in the Unreal-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for rename_data_table_row: 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 Unreal-MCP. Nothing to install.
rename_data_table_row is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_data_table_row 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 rename_data_table_row. 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.
rename_data_table_row is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue