set_data_slot

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/set-data-slot.md

WHAT IT DOES

What set_data_slot does on agentView

AI agents use set_data_slot 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	Stable slug for the data slot. Must match ^[A-Za-z0-9_-]{8,64}$. Same slug on a later call updates the existing slot. Slug stays exactly as supplied; the public
`type`	string	—	Slot kind. 'value' (default) stores 'content' verbatim. 'aggregate' stores 'content' as a composite-slot definition. Immutable after creation.
`label`	string	—	Human-readable label (max 200 chars). Required when creating a new slot; optional on update.
`content`	object	Yes	JSON content to store. For value slots: any valid JSON value up to 2 MB. For aggregate slots: a definition object { sources: [{slot,as?} \| {prefixMatch}], onMis
`group_id`	string	—	Group/organization ID for shared group slots. Omit for personal slots.
`access_token`	string	—	Optional JWT access token for authentication.

Parameters from the server's own tool schema.

RISK

Why set_data_slot is rated Medium

This tool creates or modifies data (a JSON data slot) in a reversible manner. The description explicitly states it 'creates or updates' content, which is characteristic of Write operations. While it allows reading via a public URL, the primary function is data creation/modification. The 'updates in place' behavior and mutable nature confirm it's Write rather than Read.

From the tool's definition Creates or updates a mutable JSON data slot (max 2 MB). Slug is stable; reusing it updates in place.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_data_slot Rate-limited

set_data_slot 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_data_slot": {
      "limits": [
        {
          "counter": "set_data_slot_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_data_slot call is checked against it from then on.

FAQ

Questions about set_data_slot

What does the set_data_slot tool do? +

Creates or updates a mutable JSON data slot (max 2 MB). Slug is stable; reusing it updates in place. The public read URL uses a separate server-generated PublicId, so the slug is not itself a secret URL. type='value' stores JSON verbatim; type='aggregate' stores a composite definition with sources such as {slot:'name', as?:'alias'} or {prefixMatch:'agent-'} for dynamic inclusion. Aggregates allow up to 32 sources and at most one prefixMatch, and sources must stay in the same personal/group scope. Requires content scope. Returns slug, readUrl metadata, size and timestamp. 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_data_slot accept? +

set_data_slot accepts 6 parameters: slug, type, label, content, group_id, access_token. Required: slug, content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_data_slot? +

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

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

Can I rate-limit set_data_slot? +

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

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

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