This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/webflow-list-items.md
What webflow_list_items does on UnClick
AI agents call webflow_list_items to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Items to return (max 100, default 25) |
offset | number | — | Pagination offset |
access_token | string | Yes | Webflow API token |
collection_id | string | Yes | Webflow collection id |
Parameters from the server's own tool schema.
Why webflow_list_items is rated Low
This tool queries and retrieves data from a Webflow CMS collection without any side effects. It performs a simple data retrieval operation analogous to a database SELECT query or API GET request. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could over-query or expose collection data, but cannot damage systems or trigger external operations.
From the tool's definition Tool name contains 'list' and description states 'List items in a Webflow CMS collection' — a retrieval operation with no modification or deletion.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs webflow_list_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webflow_list_items, this is the rule to start with:
webflow_list_items is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every webflow_list_items call is checked against it from then on.
Questions about webflow_list_items
List items in a Webflow CMS collection. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
webflow_list_items accepts 4 parameters: limit, offset, access_token, collection_id. Required: access_token, collection_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for webflow_list_items: 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 UnClick. Nothing to install.
webflow_list_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the webflow_list_items 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.
Set action: deny in the PolicyLayer policy for webflow_list_items. 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.
webflow_list_items is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue