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....
Part of the Zype Com server.
Free to start. No card required.
AI agents call get_player to retrieve information from Zype Com without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_player only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_player": {}
}
}See the full Zype Com policy for all 76 tools.
These attack patterns abuse exactly the kind of access get_player gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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.
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.
Deterministic rules across all 76 Zype Com tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.