Create link token for Plaid Link
AI agents use create_link_token to create or update resources in Enterprise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enterprise MCP Server environment.
This tool creates a Plaid Link token, which is a Write operation (creating a token/resource). While it is part of a financial workflow (connecting bank accounts via Plaid), the token creation itself does not move money or commit financial obligations — it merely initiates the account-linking UI flow.
From the tool's definition 'Create link token for Plaid Link' — creates a Plaid Link token, which is a short-lived token used to initialize the Plaid Link UI flow for connecting financial accounts
Attacks that exploit this kind of access
Create link token for Plaid Link. It is categorised as a Write tool in the Enterprise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enterprise MCP Server MCP server in PolicyLayer and add a rule for create_link_token: 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 Enterprise MCP Server. Nothing to install.
create_link_token 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_link_token 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_link_token. 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_link_token is provided by the Enterprise MCP Server MCP server (jimestesblog/enterprise_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 →