send_store_template_to_display

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 62 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-store-template-to-display.md

WHAT IT DOES

What send_store_template_to_display does on agentView

AI agents use send_store_template_to_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
`slug`	string	Yes	Template slug to install, e.g. 'bistro-warm-door'. Must be a currently published template.
`display_id`	string	Yes	Display profile ID (8-char alphanumeric) from list_displays or get_store_template_install_options.
`access_token`	string	—	Optional bearer token; prefer session_request_id.
`idempotency_key`	string	—	Optional opaque key (max 128 chars) to make this install retry-safe. If a previous successful install for the same (user, display, idempotency_key) tuple exists
`session_request_id`	string	—	Session handle from create_auth_session; pass it on every authenticated call.
`data_slot_overrides`	object	—	Optional { key: value } map keyed by data-slot key (see requiredDataSlots). Each value is JSON payload to install into that slot — either a string of raw JSON o

Parameters from the server's own tool schema.

RISK

Why send_store_template_to_display is rated Medium

An AI agent can call send_store_template_to_display faster than any human can review: one bad instruction and it creates or modifies resources in agentView by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

send_store_template_to_display Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_store_template_to_display": {
      "limits": [
        {
          "counter": "send_store_template_to_display_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 send_store_template_to_display call is checked against it from then on.

FAQ

Questions about send_store_template_to_display

What does the send_store_template_to_display tool do? +

Installs a published store template onto a display: materializes the HTML, auto-creates required data slots (reusing prior installs) and publishes within seconds. Call get_store_template_install_options first for valid targets and slots; customize per-slot JSON inline via data_slot_overrides (raw JSON string or inline object per key, max 64 KiB each). Requires content scope and control access to the display. 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_store_template_to_display accept? +

send_store_template_to_display accepts 6 parameters: slug, display_id, access_token, idempotency_key, session_request_id, data_slot_overrides. Required: slug, display_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on send_store_template_to_display? +

Register the agentView MCP server in PolicyLayer and add a rule for send_store_template_to_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.

What risk level is send_store_template_to_display? +

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

Can I rate-limit send_store_template_to_display? +

Yes. Add a rate_limit block to the send_store_template_to_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.

How do I block send_store_template_to_display completely? +

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

What MCP server provides send_store_template_to_display? +

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

KEEP EXPLORING

More on agentView, and thousands of servers like it.

This server

All 57 agentView tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →