AI agents use import_from_url to create or update resources in Videoseek — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Videoseek environment.
The tool creates/adds new video data to the system based on external URLs, which is a write operation. Severity is medium rather than high because: (1) the operation is reversible (videos can be deleted via the sibling delete_videos tool), (2) import operations have predictable outcomes tied to valid URL arguments, and (3) the blast radius is limited to adding potentially unwanted videos rather than modifying…
From the tool's definition Tool name 'import_from_url' and description state it 'Import a video from a social media URL' — this creates new data (video records) in the system by fetching and storing external content.
Attacks that exploit this kind of access
Import a video from a social media URL (TikTok, YouTube, Instagram, Twitter, etc.). It is categorised as a Write tool in the Videoseek MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Videoseek MCP server in PolicyLayer and add a rule for import_from_url: 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 Videoseek. Nothing to install.
import_from_url 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 import_from_url 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 import_from_url. 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.
import_from_url is provided by the Videoseek MCP server (kennyzheng-builds/videoseek-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 →