AI agents use reply_to_conversation 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.
The tool name strongly suggests it sends a reply to an existing LinkedIn conversation/message thread, which is a Write operation creating new message content. This has high severity because an AI agent could send unsolicited or inappropriate messages to LinkedIn contacts at scale. Confidence is moderate because the description is empty, so classification relies solely on the tool name.
From the tool's definition Tool name 'reply_to_conversation' implies sending a reply message in a conversation context on LinkedIn
Documented attack patterns abuse exactly the kind of access reply_to_conversation 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 reply_to_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"reply_to_conversation": {
"limits": [
{
"counter": "reply_to_conversation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reply_to_conversation 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.
Free to start. No card required.
reply_to_conversation. 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.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for reply_to_conversation: 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.
reply_to_conversation 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 reply_to_conversation 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 reply_to_conversation. 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.
reply_to_conversation 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.
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.