close_session · MCP-LinkedIn MCP: Risk & Policy

WHAT IT DOES

What close_session does on MCP-LinkedIn

AI agents invoke close_session to trigger actions in MCP-LinkedIn. 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.

WHY IT NEEDS A POLICY

Why close_session needs a policy

Closing a browser session and cleaning up resources is an execution action that affects running processes and state. While not destructive to persistent data, it irreversibly terminates the current session (losing any unsaved state), which could disrupt ongoing automation workflows. It fits Execute as it triggers external operations (browser teardown) whose effects depend on the current session state.

From the tool's definition 'Close the current browser session and clean up resources' — terminates an active browser session and performs resource cleanup, which is an external operational side effect

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_session Rate-limited

close_session 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_session": {
      "limits": [
        {
          "counter": "close_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP-LinkedIn, so you can run agents against it safely.

FAQ

Questions about close_session

What does the close_session tool do? +

Close the current browser session and clean up resources. It is categorised as a Execute tool in the MCP-LinkedIn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on close_session? +

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

What risk level is close_session? +

close_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit close_session? +

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

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

close_session is provided by the MCP-LinkedIn MCP server (logos-parthenos-ai/linkedin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.