send_url

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 72 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-url.md

WHAT IT DOES

What send_url does on agentView

AI agents use send_url 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	Yes	Absolute HTTP or HTTPS URL to load, e.g. 'https://example.com/dashboard'.
`slot`	string	—	'live' (default) or 'idle' for default/fallback content (admin scope).
`duration`	integer	—	Seconds the content stays; 0 = indefinite (default). Live slot only.
`display_id`	string	Yes	8-character display profile ID, e.g. 'ABCD1234'.
`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.
`content_description`	string	—	Short summary of what the page shows (recommended).

Parameters from the server's own tool schema.

RISK

Why send_url is rated Medium

An AI agent can call send_url 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 signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (access_token) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

send_url Rate-limited

send_url 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_url": {
      "limits": [
        {
          "counter": "send_url_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_url call is checked against it from then on.

FAQ

Questions about send_url

What does the send_url tool do? +

Shows an external web page on a display via full-page iframe: dashboards, websites or web apps. slot 'live' (default) replaces current content; slot 'idle' stores it as default/fallback content (admin scope). The URL must be absolute HTTP(S). Check get_display (response_format 'detailed') first when unsure about connectivity or embedding limits. If the page design is not display-ready, prefer send_html with generated content. Requires content 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 send_url accept? +

send_url accepts 7 parameters: url, slot, duration, display_id, access_token, session_request_id, content_description. Required: url, 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_url? +

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

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

Can I rate-limit send_url? +

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

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

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