Push one or more LINE messages to a user (generic).
AI agents use push_messages to create or update resources in LINE Bot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LINE Bot MCP Server environment.
This tool creates messages in users' inboxes, which is a reversible write operation. While it affects external users (LINE users), the impact is not destructive (messages can be managed by users), not financial, and not code execution.
From the tool's definition Tool description states 'Push one or more LINE messages to a user' — this creates/sends messages to users, a write operation that modifies state (messages are added to user inboxes). The server context confirms it 'send[s] messages' via the LINE Messaging API.
Attacks that exploit this kind of access
Push one or more LINE messages to a user (generic). It is categorised as a Write tool in the LINE Bot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LINE Bot MCP Server MCP server in PolicyLayer and add a rule for push_messages: 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 MCP Server. Nothing to install.
push_messages is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the push_messages 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 push_messages. 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.
push_messages is provided by the LINE Bot MCP Server MCP server (tndfame/mcp_management). 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 →