manage_display_category

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/de-agentview-agentview-mcp/manage-display-category.md

WHAT IT DOES

What manage_display_category does on agentView

AI agents use manage_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
`name`	string	—	Category name for action 'create', e.g. 'Reception'.
`action`	string	Yes	Operation to perform.
`new_name`	string	—	New category name (rename only).
`category_id`	string	—	Category ID to rename (rename only).
`access_token`	string	—	Optional bearer token; prefer session_request_id.
`parent_category_id`	string	—	Optional parent category ID (create only) for a subcategory.
`session_request_id`	string	—	Session handle from create_auth_session; pass it on every authenticated call.

Parameters from the server's own tool schema.

RISK

Why manage_display_category is rated Medium

An AI agent can call manage_display_category faster than any human can review: one bad instruction and it creates or modifies resources in agentView by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

manage_display_category Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_display_category": {
      "limits": [
        {
          "counter": "manage_display_category_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 agentView, apply this rule, and every manage_display_category call is checked against it from then on.

FAQ

Questions about manage_display_category

What does the manage_display_category tool do? +

Creates or renames a display category (categories group displays for broadcast_content include_category_ids). action 'create' needs name (optional parent_category_id for a subcategory); action 'rename' needs category_id and new_name — assignments and grants stay intact. Discover IDs with list_display_categories; assign displays with assign_display_categories. 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.

What parameters does manage_display_category accept? +

manage_display_category accepts 7 parameters: name, action, new_name, category_id, access_token, parent_category_id, session_request_id. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on manage_display_category? +

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

What risk level is manage_display_category? +

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

Can I rate-limit manage_display_category? +

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

How do I block manage_display_category completely? +

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

What MCP server provides manage_display_category? +

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

KEEP EXPLORING

More on agentView, and thousands of servers like it.

This server

All 57 agentView tools →

Across the catalogue

The MCP Attack Database →

Guides

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