assign_display_categories

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 52 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/assign-display-categories.md

WHAT IT DOES

What assign_display_categories does on agentView

AI agents use assign_display_categories 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
`mode`	string	—	replace (default) sets the exact list; add/remove mutates one category across displays.
`display_ids`	array	Yes	Display profile IDs to update.
`access_token`	string	—	Optional bearer token; prefer session_request_id.
`category_ids`	array	Yes	Category IDs; for mode 'add'/'remove' only the first entry is used.
`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 assign_display_categories is rated Medium

An AI agent can call assign_display_categories 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 assign_display_categories 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 assign_display_categories, this is the rule to start with:

assign_display_categories Rate-limited

assign_display_categories 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": {
    "assign_display_categories": {
      "limits": [
        {
          "counter": "assign_display_categories_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 assign_display_categories call is checked against it from then on.

FAQ

Questions about assign_display_categories

What does the assign_display_categories tool do? +

Assigns displays to categories. mode 'replace' (default) sets the full category list of each display in display_ids to category_ids; mode 'add' or 'remove' adds/removes one category (category_ids[0]) across many displays without touching other assignments. Discover IDs with list_display_categories; create categories with manage_display_category. 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 assign_display_categories accept? +

assign_display_categories accepts 5 parameters: mode, display_ids, access_token, category_ids, session_request_id. Required: display_ids, category_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on assign_display_categories? +

Register the agentView MCP server in PolicyLayer and add a rule for assign_display_categories: 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 assign_display_categories? +

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

Can I rate-limit assign_display_categories? +

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

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

assign_display_categories 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 →