set_display_embeddable_origins

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 42 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-embeddable-origins.md

WHAT IT DOES

What set_display_embeddable_origins does on agentView

AI agents use set_display_embeddable_origins 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
`origins`	array	Yes	Origin strings allowed to embed this display. Pass an empty array to allow all origins for Public displays. Each entry must be a full HTTPS origin like 'https:/
`display_id`	string	Yes	The 8-character alphanumeric display profile ID, e.g. 'ABCD1234'.
`access_token`	string	—	Optional JWT access token for authentication.
`session_request_id`	string	—	Optional session request ID returned by create_auth_session. Preferred over access_token.

Parameters from the server's own tool schema.

RISK

Why set_display_embeddable_origins is rated Medium

This tool creates or modifies security configuration settings for display embedding policies. It does not retrieve data (Read), execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial). The 'Sets' action and ability to 'clear the allowlist' indicate reversible modification of display configuration state.

From the tool's definition Tool 'sets the optional origin allowlist' and modifies display embedding configuration. Description states it 'Sets' (modifies) security policy, 'Pass an empty array to clear the allowlist' (alters state), and is 'audit-logged' (indicates state change…

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_embeddable_origins 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_embeddable_origins, this is the rule to start with:

set_display_embeddable_origins Rate-limited

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

FAQ

Questions about set_display_embeddable_origins

What does the set_display_embeddable_origins tool do? +

Sets the optional origin allowlist that restricts which third-party websites may embed this display via /display-embed/{profileId}. Only effective when the display's privacy_mode is 'Public'; private displays reject the embed route entirely regardless of this setting. Pass an empty array to clear the allowlist so public displays can be embedded from any origin. Pass an array like ['https://example.com'] to lock embedding to those specific origins plus agentView's own domains and the ChatGPT widget host. Requires admin scope and is audit-logged. 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_embeddable_origins accept? +

set_display_embeddable_origins accepts 4 parameters: origins, display_id, access_token, session_request_id. Required: origins, 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_display_embeddable_origins? +

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

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

Can I rate-limit set_display_embeddable_origins? +

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

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

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