line_get_profile
Get a LINE user's display name, profile picture, and status message.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/line-get-profile.md
What line_get_profile does on UnClick
AI agents call line_get_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 |
|---|---|---|---|
user_id | string | Yes | |
channel_access_token | string | — |
Parameters from the server's own tool schema.
Why line_get_profile is rated Low
Retrieves publicly accessible user profile information without modifying data or side effects.
From the tool's definition Get LINE user's display name, profile picture, status message.
Attacks that exploit this kind of access
The rule that runs line_get_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 line_get_profile, this is the rule to start with:
line_get_profile 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 line_get_profile call is checked against it from then on.
Questions about line_get_profile
Get a LINE user's display name, profile picture, and status message. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
line_get_profile accepts 2 parameters: user_id, channel_access_token. Required: user_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 line_get_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.
line_get_profile 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 line_get_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.
Set action: deny in the PolicyLayer policy for line_get_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.
line_get_profile 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