AI agents call line_get_profile to retrieve information from UnClick without modifying anything — 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 | Yes |
Parameters from the server's own tool schema.
This tool retrieves publicly or semi-publicly available user profile information from the LINE messaging platform. It performs a simple lookup operation (get) with no ability to modify data, execute commands, or cause destructive changes. The retrieved data (display name, profile picture, status message) are typically non-sensitive metadata.
From the tool's definition Tool description states 'Get a LINE user's display name, profile picture, and status message' — retrieving user profile data with no modification or side effects.
Attacks that exploit this kind of access
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, channel_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 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.
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 →