Low Risk

get_profile

Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.

How to control get_profile ↓

What get_profile does on Line Bot

AI agents call get_profile to retrieve information from Line Bot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_profile needs a policy

This tool only queries and retrieves existing profile data from a LINE user account. It performs no creation, modification, deletion, or execution of commands. While it accesses personal information, the read-only nature and limited scope to publicly-accessible profile fields (typical for messaging platforms) classify it as a Read operation with low severity.

From the tool's definition Tool is named 'get_profile' and described as 'Get detailed profile information' with no modification or execution capabilities mentioned. It retrieves user data (display name, profile picture URL, status message, language) without side effects.

Documented attack patterns abuse exactly the kind of access get_profile gives an agent:

How to control get_profile

PolicyLayer is an MCP gateway — it sits between your AI agents and Line Bot, and nothing reaches the server without passing your rules. This is the rule we recommend for get_profile:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_profile": {}
  }
}

get_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Line Bot — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_profile

What does the get_profile tool do? +

Get detailed profile information of a LINE user including display name, profile picture URL, status message and language. It is categorised as a Read tool in the Line Bot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_profile? +

Register the Line Bot MCP server in PolicyLayer and add a rule for 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 Line Bot. Nothing to install.

What risk level is get_profile? +

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

Can I rate-limit get_profile? +

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

How do I block get_profile completely? +

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

What MCP server provides get_profile? +

get_profile is provided by the Line Bot MCP server (@line/line-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Line Bot tool call.

Start from Line Bot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 Line Bot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.