Medium Risk

send_push_message

Send a direct text message to a specific user by their LINE user ID.

Part of the Linewhiz server.

send_push_message can modify Linewhiz data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LINEWHIZ →

Free to start. No card required.

AI agents use send_push_message to create or modify resources in Linewhiz. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call send_push_message repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Linewhiz.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_push_message": {
      "limits": [
        {
          "counter": "send_push_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Linewhiz policy for all 10 tools.

Get this rule live on your own Linewhiz server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LINEWHIZ →

View all 10 tools →

These attack patterns abuse exactly the kind of access send_push_message gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so send_push_message only ever does what you allow.

SECURE LINEWHIZ →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the send_push_message tool do? +

Send a direct text message to a specific user by their LINE user ID.. It is categorised as a Write tool in the Linewhiz MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_push_message? +

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

What risk level is send_push_message? +

send_push_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_push_message? +

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

How do I block send_push_message completely? +

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

What MCP server provides send_push_message? +

send_push_message is provided by the Linewhiz MCP server (kinzen/linewhiz). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linewhiz tool call.

Deterministic rules across all 10 Linewhiz tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.