AI agents call list_upload_jobs to retrieve information from Yadisk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about upload jobs in their current state. It performs no mutations, deletions, or side effects—it merely retrieves and displays information. This is a classic Read operation with minimal security risk, making severity low.
From the tool's definition Tool name 'list_upload_jobs' and description 'List all background upload jobs and their statuses' indicate a read-only operation that retrieves information about existing upload jobs without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
List all background upload jobs and their statuses. It is categorised as a Read tool in the Yadisk MCP Server, which means it retrieves data without modifying state.
Register the Yadisk MCP server in PolicyLayer and add a rule for list_upload_jobs: 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 Yadisk. Nothing to install.
list_upload_jobs 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 list_upload_jobs 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 list_upload_jobs. 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.
list_upload_jobs is provided by the Yadisk MCP server (patr56/yadisk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →