broadcast_content
Sends HTML to many displays at once. Target explicit display_ids, all=true for every accessible display, or include_category_ids to reach every display in those categories (include_descendants for subcategories, dry_run to preview matches without sending). Locked displays are skipped with reasons...
This record as markdown: /tools/de-agentview-agentview-mcp/broadcast-content.md
What broadcast_content does on agentView
AI agents call broadcast_content to retrieve information from agentView without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
all | boolean | — | true targets all accessible displays. |
html | string | — | Complete HTML document. Mutually exclusive with base64_html. |
dry_run | boolean | — | Preview: return the matched displays without sending. Works with all targeting modes. |
duration | integer | — | Seconds the content stays; 0 = indefinite. |
base64_html | string | — | Base64-encoded HTML. Mutually exclusive with html. |
description | string | — | Short summary of the content being sent (required when sending). |
display_ids | array | — | Display profile IDs to target. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
session_request_id | string | — | Session handle from create_auth_session; pass it on every authenticated call. |
include_descendants | boolean | — | With include_category_ids: also include subcategories. |
include_category_ids | array | — | Category IDs: broadcast to displays assigned to these categories. |
Parameters from the server's own tool schema.
Why broadcast_content is rated Low
Even though broadcast_content only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (access_token) · Accepts raw HTML/template content (html) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs broadcast_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 broadcast_content, this is the rule to start with:
broadcast_content is read-only, so it stays allowed. 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 broadcast_content call is checked against it from then on.
Questions about broadcast_content
Sends HTML to many displays at once. Target explicit display_ids, all=true for every accessible display, or include_category_ids to reach every display in those categories (include_descendants for subcategories, dry_run to preview matches without sending). Locked displays are skipped with reasons. For a single display use send_html. Requires content scope. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
broadcast_content accepts 11 parameters: all, html, dry_run, duration, base64_html, description, display_ids, access_token, session_request_id, include_descendants, include_category_ids. 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 broadcast_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.
broadcast_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the broadcast_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.
Set action: deny in the PolicyLayer policy for broadcast_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.
broadcast_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.
More on agentView, and thousands of servers like it.
This server
Across the catalogue