clear_display
Removes the current live content from a display and returns it to its idle/default state. Viewers will immediately see the change. Use this when the user wants to blank or reset a display. This does not delete the display itself — use delete_display for that. Requires authentication with at least...
This record as markdown: /tools/de-agentview-agentview-mcp/clear-display.md
What clear_display does on agentView
AI agents use clear_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 |
|---|---|---|---|
display_id | string | Yes | The 8-character alphanumeric display profile ID to clear, e.g. 'ABCD1234'. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why clear_display is rated Medium
The tool removes live content from a display but is reversible — the display still exists and content can be resent. It modifies the display's state (clearing it) rather than destroying anything permanently, so Write is the most appropriate category. The blast radius is medium because clearing a display affects live viewers immediately but can be undone by sending new content.
From the tool's definition Removes the current live content from a display and returns it to its idle/default state. This does not delete the display itself.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs clear_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 clear_display, this is the rule to start with:
clear_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 clear_display call is checked against it from then on.
Questions about clear_display
Removes the current live content from a display and returns it to its idle/default state. Viewers will immediately see the change. Use this when the user wants to blank or reset a display. This does not delete the display itself — use delete_display for that. Requires authentication with at least content_only scope. Returns id and status ('cleared'). 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.
clear_display accepts 2 parameters: display_id, access_token. Required: 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 clear_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.
clear_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 clear_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 clear_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.
clear_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