This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/wise-accounts.md
What wise_accounts does on UnClick
AI agents call wise_accounts to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
profile_id | number | Yes |
Parameters from the server's own tool schema.
Why wise_accounts is rated Low
This tool queries and retrieves account data associated with a Wise profile. It has no capability to create, modify, delete, or execute operations. While it accesses potentially sensitive financial account information, the retrieval itself is read-only and reversible, making it a Read category tool with low severity risk when used appropriately.
From the tool's definition Tool name 'wise_accounts' and description 'Get Wise accounts for a profile' indicate a retrieval/query operation with the verb 'Get', which retrieves existing account information without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs wise_accounts 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 wise_accounts, this is the rule to start with:
wise_accounts is read-only, so it stays allowed. 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 wise_accounts call is checked against it from then on.
Questions about wise_accounts
Get Wise accounts for a profile. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
wise_accounts accepts 2 parameters: api_key, profile_id. Required: profile_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 wise_accounts: 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.
wise_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wise_accounts 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 wise_accounts. 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.
wise_accounts 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