AI agents use create_pinterest_pin to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
link | string | — | Destination URL when pin is clicked |
title | string | — | |
board_id | string | Yes | Board ID to pin to |
description | string | — | |
access_token | string | — | |
board_section_id | string | — | |
media_source_url | string | Yes | Public image URL |
Parameters from the server's own tool schema.
This tool creates new content (a Pinterest pin) reversibly — the pin can be edited or deleted afterward. It modifies the user's Pinterest account state by adding a new pin, which qualifies as a Write operation. The severity is medium because misuse could result in spam, unauthorized posting, or platform policy violations, but the action is not destructive or financial in nature.
From the tool's definition The tool name and description explicitly state 'Create a new Pinterest pin from an image URL,' which is a data creation operation on a third-party platform (Pinterest).
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
Create a new Pinterest pin from an image URL. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_pinterest_pin accepts 7 parameters: link, title, board_id, description, access_token, board_section_id, media_source_url. Required: board_id, media_source_url. 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 create_pinterest_pin: 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.
create_pinterest_pin 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 create_pinterest_pin 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 create_pinterest_pin. 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.
create_pinterest_pin 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →