get_player
Get player embed code or raw player data for a video. Formats: - json: Returns raw player data including JavaScript player code, and response metadata. Best for inspecting player behavior. - html: Returns a complete HTML page with embedded player - ready to use as an iframe src or for inspection....
This record as markdown: /tools/com-zype-mcp-server/get-player.md
What get_player does on Zype Com
AI agents call get_player to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | Player format: "html" for full HTML page, "js" for JavaScript embed, "json" for player data |
autoplay | boolean | — | Enable autoplay (default: false) |
video_id | string | Yes | The video ID to get the player for |
audio_only | boolean | — | Audio-only playback (default: false) |
player_key | string | — | Player API key (uses server API key if not provided) |
Parameters from the server's own tool schema.
Why get_player is rated Low
Even though get_player only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_player safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_player, this is the rule to start with:
get_player is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every get_player call is checked against it from then on.
Questions about get_player
Get player embed code or raw player data for a video. Formats: - json: Returns raw player data including JavaScript player code, and response metadata. Best for inspecting player behavior. - html: Returns a complete HTML page with embedded player - ready to use as an iframe src or for inspection. - js: Returns JavaScript embed code to include in a webpage. Use cases: - Generate embed codes for web pages - Get the full HTML player page for iframe embedding - Inspect player JavaScript code - Debug playback issues. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
get_player accepts 5 parameters: format, autoplay, video_id, audio_only, player_key. Required: video_id. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for get_player: 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 Zype Com. Nothing to install.
get_player 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 get_player 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 get_player. 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.
get_player is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
This server
Across the catalogue