rename_display
Changes the friendly name of an existing display. Use this when the user wants to update only the display name without affecting its content or state. Requires admin scope. Returns id and the updated name.
This record as markdown: /tools/de-agentview-agentview-mcp/rename-display.md
What rename_display does on agentView
AI agents use rename_display to create or update resources in agentView, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your agentView environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The new friendly display name. Non-empty string. |
display_id | string | Yes | The 8-character alphanumeric display profile ID to rename, e.g. 'ABCD1234'. |
access_token | string | — | Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your ident |
Parameters from the server's own tool schema.
Why rename_display is rated Medium
The tool modifies a display's name attribute (metadata) reversibly without affecting content, state, or deleting data. This is a classic Write operation—data is created or modified but can be undone (renamed again). The 'admin scope' requirement and low blast radius (renaming a display name has minimal downstream impact) support low severity.
From the tool's definition Tool description explicitly states it 'Changes the friendly name of an existing display' and 'Returns id and the updated name.' This is a metadata update operation.
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs rename_display safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_display, this is the rule to start with:
rename_display 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 agentView, apply this rule, and every rename_display call is checked against it from then on.
Questions about rename_display
Changes the friendly name of an existing display. Use this when the user wants to update only the display name without affecting its content or state. Requires admin scope. Returns id and the updated name. It is categorised as a Write tool in the agentView MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rename_display accepts 3 parameters: name, display_id, access_token. Required: name, display_id. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for rename_display: 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 agentView. Nothing to install.
rename_display 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_display 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_display. 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_display is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue