AI agents use plaid_link_token_create 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 |
|---|---|---|---|
secret | string | Yes | |
webhook | string | — | |
language | string | — | Language code (default: en) |
products | array | — | Plaid products (default: ['transactions']) |
client_id | string | Yes | |
client_name | string | — | App name shown in Plaid Link UI |
environment | string | — | |
access_token | string | — | For update mode: existing access token |
country_codes | array | — | ISO country codes (default: ['US']) |
user_client_user_id | string | Yes | Unique identifier for the end user |
Parameters from the server's own tool schema.
An AI agent can call plaid_link_token_create faster than any human can review — one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (webhook) · Handles credentials or secrets (secret) · High parameter count (10 properties)
Attacks that exploit this kind of access
Create a Plaid Link token to initialise the Plaid Link flow. 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.
plaid_link_token_create accepts 10 parameters: secret, webhook, language, products, client_id, client_name, environment, access_token, country_codes, user_client_user_id. Required: secret, client_id, user_client_user_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 plaid_link_token_create: 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.
plaid_link_token_create 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 plaid_link_token_create 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 plaid_link_token_create. 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.
plaid_link_token_create 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 →