Medium Risk

upwork_close_session

Close browser session and cleanup resources.

How to control upwork_close_session ↓

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

Medium Risk

An AI agent can call upwork_close_session faster than any human can review — one bad instruction and it creates or modifies resources in Upwork MCP Server by the hundred, each call as confident as the last.

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

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

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

upwork_close_session 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 Upwork 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 upwork_close_session tool do? +

Close browser session and cleanup resources. It is categorised as a Write tool in the Upwork 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 upwork_close_session? +

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

What risk level is upwork_close_session? +

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

Can I rate-limit upwork_close_session? +

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

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

upwork_close_session is provided by the Upwork MCP Server MCP server (vanooo/upwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Upwork MCP Server tool call.

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

Free to start. No card required.

18 Upwork 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.