Estimate how many quota messages a planned send will consume — without actually sending. Useful before user confirmation, especially for narrowcast / broadcast. Args: - target: Same shapes as line_send_message ({ user_id } | { user_ids } | { audience } | { filter } | { everyone: true }). - messag...
AI agents call line_estimate_send_cost 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.
This tool only performs a cost/quota estimation calculation and explicitly states it does not send any messages. It retrieves/computes information about a hypothetical send operation with no side effects, making it a Read operation with low severity.
From the tool's definition Estimate how many quota messages a planned send will consume — without actually sending. Useful before user confirmation
Documented attack patterns abuse exactly the kind of access line_estimate_send_cost 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_estimate_send_cost:
{
"version": "1",
"default": "deny",
"tools": {
"line_estimate_send_cost": {}
}
}line_estimate_send_cost is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Estimate how many quota messages a planned send will consume — without actually sending. Useful before user confirmation, especially for narrowcast / broadcast. Args: - target: Same shapes as line_send_message ({ user_id } | { user_ids } | { audience } | { filter } | { everyone: true }). - message_count: How many message objects in the send (1-5, default 1). LINE charges per message * recipients. - oa: optional OA id. Returns: { estimated_recipients?: number, // known exactly for user_id(s); approximate for audience; unknown for filter/everyone estimated_cost_messages?: number, // recipients * message_count quota: { used, total, remaining, percentage_used }, cost_share_percent?: number, // estimated_cost / remaining notes: string[] } Notes: - For target.audience: we look up audience_count via line_list_audiences first. - For target.filter or target.everyone: exact estimation isn. It is categorised as a Read tool in the Line Oa Mcp Ultimate MCP Server, which means it retrieves data without modifying state.
Register the Line Oa Mcp Ultimate MCP server in PolicyLayer and add a rule for line_estimate_send_cost: 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.
line_estimate_send_cost 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_estimate_send_cost 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_estimate_send_cost. 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_estimate_send_cost 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.
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.