Medium Risk

send_message

send_message

How to control send_message ↓

AI agents use send_message to create or update resources in LinkedIn Intelligence MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn Intelligence MCP Server environment.

Medium Risk

send_message creates new messages on LinkedIn, which is a Write category action (creates data reversibly). Severity is high because unsupervised messaging could enable spam, harassment, or impersonation at scale. Confidence is 0.85 rather than higher because the tool description is empty, leaving some ambiguity, but the context from the server description and tool name is clear.

From the tool's definition Tool name 'send_message' combined with server description stating 'messaging through natural language' indicates the tool sends messages to LinkedIn users. Message sending is a write operation that creates new data (messages) in a reversible manner.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_message:

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

send_message stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LinkedIn Intelligence MCP Server — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the send_message tool do? +

send_message. It is categorised as a Write tool in the LinkedIn Intelligence MCP Server 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_message? +

Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for send_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 LinkedIn Intelligence MCP Server. Nothing to install.

What risk level is send_message? +

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

Can I rate-limit send_message? +

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

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

send_message is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LinkedIn Intelligence MCP Server tool call.

Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

87 LinkedIn Intelligence MCP Server 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.