Low Risk

line_get_user_profile

Fetch a LINE user

How to control line_get_user_profile ↓

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

Low Risk

This tool retrieves user profile information from a LINE Official Account without creating, modifying, or deleting data. It has no side effects beyond returning existing data. This is a standard Read operation with low severity, as user profile data exposure alone does not enable financial transactions, destructive actions, or code execution.

From the tool's definition Tool name 'line_get_user_profile' and description 'Fetch a LINE user' indicate data retrieval without modification. The verb 'Fetch' is a classic read operation.

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

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

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

line_get_user_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 Oa Mcp Ultimate — 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.

Go deeper

What does the line_get_user_profile tool do? +

Fetch a LINE user. It is categorised as a Read tool in the Line Oa Mcp Ultimate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on line_get_user_profile? +

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

What risk level is line_get_user_profile? +

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

Can I rate-limit line_get_user_profile? +

Yes. Add a rate_limit block to the line_get_user_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 line_get_user_profile completely? +

Set action: deny in the PolicyLayer policy for line_get_user_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 line_get_user_profile? +

line_get_user_profile is provided by the Line Oa Mcp Ultimate MCP server (wasintoh/line-oa-mcp-ultimate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Line Oa Mcp Ultimate tool call.

Deterministic rules across all 34 Line Oa Mcp Ultimate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

34 Line Oa Mcp Ultimate tools catalogued and risk-classified — across an index of 42,500+ 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.