set_display_privacy_mode

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 32 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/set-display-privacy-mode.md

WHAT IT DOES

What set_display_privacy_mode does on agentView

AI agents use set_display_privacy_mode 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
`display_id`	string	Yes	The 8-character alphanumeric display profile ID, e.g. 'ABCD1234'.
`access_token`	string	—	Optional JWT access token for authentication.
`privacy_mode`	string	Yes	Desired privacy mode.

Parameters from the server's own tool schema.

RISK

Why set_display_privacy_mode is rated Medium

This is a Write operation: it reversibly updates display privacy configuration and audit logs the change. However, it has high severity because misconfiguration could extend exposure of PII-containing displays from 1-hour to 24-hour TTLs, significantly increasing risk of unauthorized access to sensitive data.

From the tool's definition 'Sets the per-display privacy mode' and 'Flipping is audit-logged' indicate the tool modifies configuration state.

Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_display_privacy_mode Rate-limited

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

FAQ

Questions about set_display_privacy_mode

What does the set_display_privacy_mode tool do? +

Sets the per-display privacy mode that caps how long share-links can live. 'Private' (default for new displays) caps share-link TTL at 1 hour — choose this for displays that might show PII. 'Public' opts the display in to digital-signage mode and lifts the cap to 24 hours. Flipping is audit-logged. Requires admin scope. 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 set_display_privacy_mode accept? +

set_display_privacy_mode accepts 3 parameters: display_id, access_token, privacy_mode. Required: display_id, privacy_mode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_display_privacy_mode? +

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

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

Can I rate-limit set_display_privacy_mode? +

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

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

set_display_privacy_mode 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 79 agentView tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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