link_items
Create typed relations between items: alternative (A or B), complement (A and B together), upgrade (B replaces A), duplicate (same item different site), same_seller. Supports single pair (from_id, to_id, relation) or bulk (pairs array).
This record as markdown: /tools/com-grabbitapp-grabblist/link-items.md
What link_items does on Grabblist
AI agents use link_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 |
|---|---|---|---|
pairs | array | — | Array of pairs to link (for bulk mode) |
to_id | string | — | Second item ID (for single pair mode) |
reason | string | — | Why this change was made (shown to user in change history) |
from_id | string | — | First item ID (for single pair mode) |
relation | string | — | Type of relationship (for single pair mode) |
Parameters from the server's own tool schema.
Why link_items is rated Medium
An AI agent can call link_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 link_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 link_items, this is the rule to start with:
link_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 link_items call is checked against it from then on.
Questions about link_items
Create typed relations between items: alternative (A or B), complement (A and B together), upgrade (B replaces A), duplicate (same item different site), same_seller. Supports single pair (from_id, to_id, relation) or bulk (pairs array). 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.
link_items accepts 5 parameters: pairs, to_id, reason, from_id, relation. 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 link_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.
link_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 link_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 link_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.
link_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