wise_profile

Get the authenticated Wise user profile.

SERVERUnClick SOURCEcreativelead/unclick

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/creativelead-unclick/wise-profile.md

WHAT IT DOES

What wise_profile does on UnClick

AI agents call wise_profile 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	—

Parameters from the server's own tool schema.

RISK

Why wise_profile is rated Low

This tool retrieves/queries user profile information from Wise (a financial services platform). While it accesses financial-related account data, the operation is read-only with no destructive, write, or financial transaction capabilities.

From the tool's definition Tool name 'wise_profile' and description 'Get the authenticated Wise user profile' indicate retrieval of user profile data with no modification or side effects.

Risk signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wise_profile 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_profile, this is the rule to start with:

wise_profile Allowed

wise_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wise_profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every wise_profile call is checked against it from then on.

FAQ

Questions about wise_profile

What does the wise_profile tool do? +

Get the authenticated Wise user profile. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does wise_profile accept? +

wise_profile accepts 1 parameter: api_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wise_profile? +

Register the UnClick MCP server in PolicyLayer and add a rule for wise_profile: 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.

What risk level is wise_profile? +

wise_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wise_profile? +

Yes. Add a rate_limit block to the wise_profile 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.

How do I block wise_profile completely? +

Set action: deny in the PolicyLayer policy for wise_profile. 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.

What MCP server provides wise_profile? +

wise_profile is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 451 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →