line_reply_message
Reply to a LINE message using a reply token from a webhook event.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/line-reply-message.md
What line_reply_message does on UnClick
AI agents call line_reply_message 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 |
|---|---|---|---|
message | string | — | Convenience: single text message to reply with |
messages | object | — | Array of LINE message objects (max 5), or use message for a single text reply |
reply_token | string | Yes | |
channel_access_token | string | — |
Parameters from the server's own tool schema.
Why line_reply_message is rated Low
Even though line_reply_message only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs line_reply_message 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_reply_message, this is the rule to start with:
line_reply_message 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_reply_message call is checked against it from then on.
Questions about line_reply_message
Reply to a LINE message using a reply token from a webhook event. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
line_reply_message accepts 4 parameters: message, messages, reply_token, channel_access_token. Required: reply_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_reply_message: 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_reply_message 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_reply_message 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_reply_message. 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_reply_message 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