splitwise_action
Perform a Splitwise action: get_groups, get_expenses, get_balances, create_expense, get_friends.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/splitwise-action.md
What splitwise_action does on UnClick
AI agents use splitwise_action 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 |
|---|---|---|---|
cost | string | — | |
users | array | — | |
action | string | Yes | |
api_key | string | — | |
group_id | number | — | |
description | string | — | |
currency_code | string | — |
Parameters from the server's own tool schema.
Why splitwise_action is rated Medium
The tool supports multiple Splitwise operations. While most are read operations (get_groups, get_expenses, get_balances, get_friends), 'create_expense' creates financial records. Per the rules, the most severe applicable category applies. Creating an expense is a Write operation (reversible financial record creation), not a direct financial transfer, so Write is appropriate over Financial.
From the tool's definition 'create_expense' is listed among the supported actions
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs splitwise_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For splitwise_action, this is the rule to start with:
splitwise_action 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 UnClick, apply this rule, and every splitwise_action call is checked against it from then on.
Questions about splitwise_action
Perform a Splitwise action: get_groups, get_expenses, get_balances, create_expense, get_friends. 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.
splitwise_action accepts 7 parameters: cost, users, action, api_key, group_id, description, currency_code. Required: action. 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 splitwise_action: 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.
splitwise_action 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 splitwise_action 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 splitwise_action. 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.
splitwise_action 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue