AI agents call upwork_get_conversation to retrieve information from Upwork MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description lowering confidence slightly, the tool name strongly suggests querying conversations. No indicators of modification, deletion, execution, or financial operations. Classified as Read (retrieves data with no side effects) with low severity since it accesses potentially sensitive communications but without direct harm potential from retrieval alone.
From the tool's definition Tool name 'upwork_get_conversation' indicates data retrieval. Server description mentions 'manage messages' and sibling tools include 'upwork_get_messages', suggesting this retrieves existing conversation/message data without modification.
Documented attack patterns abuse exactly the kind of access upwork_get_conversation 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_get_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"upwork_get_conversation": {}
}
}upwork_get_conversation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
upwork_get_conversation. It is categorised as a Read tool in the Upwork MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Upwork MCP Server MCP server in PolicyLayer and add a rule for upwork_get_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 Upwork MCP Server. Nothing to install.
upwork_get_conversation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the upwork_get_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 upwork_get_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.
upwork_get_conversation 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.
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.