rename_display_category
Renames one personal display category by stable category ID. Existing assignments and grants keep working because they reference the category ID; only the category name/path changes. Requires display.manage capability.
This record as markdown: /tools/de-agentview-agentview-mcp/rename-display-category.md
What rename_display_category does on agentView
AI agents use rename_display_category 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 |
|---|---|---|---|
new_name | string | Yes | New category name. The path segment is normalised by the server. |
category_id | string | Yes | Current category ID to rename. |
access_token | string | — | Optional JWT access token for authentication. |
session_request_id | string | — | Optional session request ID returned by create_auth_session. |
Parameters from the server's own tool schema.
Why rename_display_category is rated Medium
This tool modifies data (the display category name/path) reversibly and can be undone by renaming again. It does not delete, execute code, or create financial obligations. The blast radius is medium: renaming a category could cause confusion if misused at scale across an organization's display infrastructure, but the change is non-destructive and assignments remain valid.
From the tool's definition Tool description states 'Renames one personal display category' — this is a metadata modification that changes the category name/path.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs rename_display_category 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_category, this is the rule to start with:
rename_display_category 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_category call is checked against it from then on.
Questions about rename_display_category
Renames one personal display category by stable category ID. Existing assignments and grants keep working because they reference the category ID; only the category name/path changes. Requires display.manage capability. 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_category accepts 4 parameters: new_name, category_id, access_token, session_request_id. Required: new_name, category_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_category: 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_category 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_category 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_category. 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_category 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