set_pinned_items
Set the pinned "Top Picks" items for a collection (max 3). Pinned items are highlighted on the share page.
This record as markdown: /tools/com-grabbitapp-grabblist/set-pinned-items.md
What set_pinned_items does on Grabblist
AI agents use set_pinned_items to create or update resources in Grabblist, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Grabblist environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Why this change was made (shown to user in change history) |
item_ids | array | Yes | Items to pin, in display order (1st = top) |
collection_id | string | Yes | The collection ID |
Parameters from the server's own tool schema.
Why set_pinned_items is rated Medium
An AI agent can call set_pinned_items faster than any human can review: one bad instruction and it creates or modifies resources in Grabblist by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs set_pinned_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grabblist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_pinned_items, this is the rule to start with:
set_pinned_items 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Grabblist, apply this rule, and every set_pinned_items call is checked against it from then on.
Questions about set_pinned_items
Set the pinned "Top Picks" items for a collection (max 3). Pinned items are highlighted on the share page. It is categorised as a Write tool in the Grabblist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_pinned_items accepts 3 parameters: reason, item_ids, collection_id. Required: item_ids, collection_id. The full parameter table on this page comes from the server's own tool schema.
Register the Grabblist MCP server in PolicyLayer and add a rule for set_pinned_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 Grabblist. Nothing to install.
set_pinned_items is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_pinned_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 set_pinned_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.
set_pinned_items is provided by the Grabblist MCP server (https://mcp.grabbitapp.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grabblist, and thousands of servers like it.
This server
Across the catalogue