AI agents use square_payments to commit financial operations through UnClick — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | |
limit | number | — | |
action | string | — | list or create (default: list) |
cursor | string | — | |
end_time | string | — | |
source_id | string | — | Required for action='create' |
begin_time | string | — | RFC 3339 timestamp |
customer_id | string | — | |
access_token | string | Yes | Square access token |
amount_money | object | — | {amount: number, currency: string} |
idempotency_key | string | — |
Parameters from the server's own tool schema.
The tool can create Square payments, which constitutes a financial transaction. Creating payments moves money or commits financial obligations. The 'list' capability is merely Read, but the most severe applicable category is Financial due to the payment creation capability. Misuse could result in unauthorized charges.
From the tool's definition 'create Square payments' — directly initiates financial payment transactions
Risk signalsHandles credentials or secrets (access_token) · High parameter count (11 properties)
Attacks that exploit this kind of access
List or create Square payments. It is categorised as a Financial tool in the UnClick MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
square_payments accepts 11 parameters: note, limit, action, cursor, end_time, source_id, begin_time, customer_id, access_token, amount_money, idempotency_key. Required: access_token. 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 square_payments: 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.
square_payments is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the square_payments 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 square_payments. 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.
square_payments 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 →