AI agents invoke stop_viewer to trigger actions in LinkedIn-Posts-Hunter-MCP-Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a command to halt an active service. While not destructive (data isn't deleted) or a side-effect-free read, it performs an operational action that stops external processes. The severity is medium because stopping a viewer service has moderate blast radius—it interrupts the user's monitoring workflow but doesn't delete data, move money, or cause persistent damage.
From the tool's definition "Stop the running viewer server" indicates termination of a process/service.
Documented attack patterns abuse exactly the kind of access stop_viewer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn-Posts-Hunter-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_viewer:
{
"version": "1",
"default": "deny",
"tools": {
"stop_viewer": {
"limits": [
{
"counter": "stop_viewer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_viewer stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Stop the running viewer server. It is categorised as a Execute tool in the LinkedIn-Posts-Hunter-MCP-Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LinkedIn-Posts-Hunter-MCP-Server MCP server in PolicyLayer and add a rule for stop_viewer: 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-Posts-Hunter-MCP-Server. Nothing to install.
stop_viewer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_viewer 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 stop_viewer. 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.
stop_viewer is provided by the LinkedIn-Posts-Hunter-MCP-Server MCP server (kevin-weitgenant/linkedin-posts-hunter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn-Posts-Hunter-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 LinkedIn-Posts-Hunter-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.