New PolicyLayer is now the system of record for AI agent authority. Never answer your agent twice

send_html

Pushes raw HTML to one display, replacing current content. Prefer send_url only when the user explicitly wants an external web page. Include a human-readable description so get_display_content can summarize intent without reading raw HTML. Before complex content, call get_display_capabilities to ...

SERVERagentView SOURCEhttps://agentview.de/mcp
Medium RISK CLASS
Category Write
Parameters 82 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/send-html.md

What send_html does on agentView

AI agents use send_html 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.

ParameterTypeRequiredDescription
html string Complete HTML document or fragment to render on the display. Mutually exclusive with base64_html — provide exactly one.
token string Display-specific preview token for unauthenticated demo-sign access. This is NOT the auth/JWT token. Omit this for normal authenticated usage.
duration integer How long the content stays on the display in seconds. 0 means indefinite (content persists until replaced). Defaults to 0 when omitted.
display_id string Yes The 8-character alphanumeric display profile ID to send content to, e.g. 'ABCD1234'.
base64_html string Base64-encoded HTML string (standard base64, not base64url). Use this instead of html only when the HTML contains characters that cannot survive JSON string tra
description string Yes Mandatory short human-readable description of the HTML upload (1-1000 characters), e.g. 'Weekly KPI dashboard with revenue and uptime'.
access_token string Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your ident
content_description string Optional alias for description. If both are provided, description wins.

Parameters from the server's own tool schema.

Why send_html is rated Medium

send_html writes new content to a display, replacing existing content. This is a reversible modification (new content can be sent later), so it falls under Write rather than Destructive.

From the tool's definition Tool description states it "Pushes raw HTML to one display, replacing current content" — this is a write operation that modifies display state reversibly. The tool creates/updates what is shown on a screen.

Risk signalsHandles credentials or secrets (token) · Accepts raw HTML/template content (html)

Questions about send_html

What does the send_html tool do? +

Pushes raw HTML to one display, replacing current content. Prefer send_url only when the user explicitly wants an external web page. Include a human-readable description so get_display_content can summarize intent without reading raw HTML. Before complex content, call get_display_capabilities to match the real browser/runtime. When no design system is supplied, use premium digital-signage quality: full-screen layout, strong hierarchy, refined typography, robust fallback data, and no action buttons unless touch is requested. Exactly one of html or base64_html is required. Requires content_only scope and display management access. Returns id, name, duration, file and version. 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 send_html accept? +

send_html accepts 8 parameters: html, token, duration, display_id, base64_html, description, access_token, content_description. Required: display_id, description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on send_html? +

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

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

Can I rate-limit send_html? +

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

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

send_html 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of agentView's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.