set_idle_content

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 51 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-idle-content.md

WHAT IT DOES

What set_idle_content does on agentView

AI agents use set_idle_content 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
`url`	string	—	Absolute HTTP or HTTPS URL to use as idle content; the server wraps it in a sandboxed full-page iframe. Mutually exclusive with html.
`html`	string	—	Complete HTML to use as idle content. Omit this (and url) to clear custom idle content. Mutually exclusive with url.
`display_id`	string	Yes	The 8-character alphanumeric display profile ID, e.g. 'ABCD1234'.
`access_token`	string	—	Optional JWT access token for authentication.
`content_description`	string	—	Optional human-readable summary for the idle/default content.

Parameters from the server's own tool schema.

RISK

Why set_idle_content is rated Medium

This tool creates or modifies display configuration (idle content templates) reversibly. It does not delete data irreversibly, execute arbitrary code, trigger financial transactions, or execute commands—it simply stores HTML/URL templates and metadata for later rendering. The Write category is appropriate because the changes are reversible (can be cleared or overwritten).

From the tool's definition Sets or clears the default idle content for a display. Provide html OR url to set idle content...or omit both to clear idle content. Creates or modifies displayconfiguration that persists until changed again.

Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (access_token) · Accepts raw HTML/template content (html) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_idle_content Rate-limited

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

FAQ

Questions about set_idle_content

What does the set_idle_content tool do? +

Sets or clears the default idle content for a display. Idle content is shown whenever the display has no active live content. Provide html OR url to set idle content (mutually exclusive — url is wrapped in a full-page iframe document), or omit both to clear idle content. Provide content_description to make later state reads easier for agents. When the display is currently idle (no active live content), the new idle is pushed to the display immediately; otherwise it stays dormant until the live content ends. 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_idle_content accept? +

set_idle_content accepts 5 parameters: url, html, display_id, access_token, content_description. Required: display_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_idle_content? +

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

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

Can I rate-limit set_idle_content? +

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

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

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