AI agents use metube_upload_cookies to create or update resources in Metube — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metube environment.
This tool creates or updates authentication state (cookies) in the MeTube instance, which is a reversible write operation. While cookies enable access to restricted content, uploading them does not directly execute downloads, delete data, or move money.
From the tool's definition Tool name 'metube_upload_cookies' and description 'Upload cookies for authenticated downloads' indicate creation/modification of authentication credentials stored in the system.
Attacks that exploit this kind of access
Upload cookies for authenticated downloads (e.g., age-restricted content). It is categorised as a Write tool in the Metube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metube MCP server in PolicyLayer and add a rule for metube_upload_cookies: 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 Metube. Nothing to install.
metube_upload_cookies 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 metube_upload_cookies 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 metube_upload_cookies. 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.
metube_upload_cookies is provided by the Metube MCP server (junglem0nkey/metube-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 →