Alias for manual_login — re-save session from current Chrome tab.
AI agents use save_session to create or update resources in Upwork — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Upwork environment.
save_session writes credential or session data to storage, enabling persistent authenticated access to Upwork. While not destructive (data is not irreversibly deleted) or financial (no money moves), it is a Write operation that creates/modifies authentication artifacts.
From the tool's definition The tool description states it 're-save[s] session from current Chrome tab,' which means it captures and stores authentication credentials or session tokens. This modifies persisted authentication state.
Documented attack patterns abuse exactly the kind of access save_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Upwork, and nothing reaches the server without passing your rules. This is the rule we recommend for save_session:
{
"version": "1",
"default": "deny",
"tools": {
"save_session": {
"limits": [
{
"counter": "save_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_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.
Free to start. No card required.
Alias for manual_login — re-save session from current Chrome tab. It is categorised as a Write tool in the Upwork MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Upwork MCP server in PolicyLayer and add a rule for save_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. Nothing to install.
save_session 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 save_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.
Set action: deny in the PolicyLayer policy for save_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.
save_session is provided by the Upwork MCP server (zcrossoverz/upwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Upwork, 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.
11 Upwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.