list_player_requests
Get video player load/request counts. USAGE: - By video: group_by=["video_id","video_title"] - Daily trend: interval="day" - By platform: group_by=["platform"] Data limited to last 90 days.
This record as markdown: /tools/com-zype-mcp-server/list-player-requests.md
What list_player_requests does on Zype Com
AI agents call list_player_requests 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 |
|---|---|---|---|
limit | number | — | Max results to return (default: 200, max: 500) |
offset | number | — | Offset for pagination |
country | string | — | Filter by country code |
sort_by | string | — | Sort by field+direction. Default: day_desc. NOTE: Cannot sort by metric value - for top N by plays/views, fetch all and sort client-side. |
group_by | array | — | Group by fields: video_id, video_title, country, platform |
interval | string | — | Time interval for grouping data (default: day) |
platform | string | — | Filter by platform |
video_id | string | — | Filter by video ID |
start_date_gte | string | — | Start date filter (YYYY-MM-DD). Max 90 days ago. Defaults to 2 weeks ago. |
start_date_lte | string | — | End date filter (YYYY-MM-DD). Defaults to today. |
Parameters from the server's own tool schema.
Why list_player_requests is rated Low
Even though list_player_requests 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.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs list_player_requests 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 list_player_requests, this is the rule to start with:
list_player_requests 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 list_player_requests call is checked against it from then on.
Questions about list_player_requests
Get video player load/request counts. USAGE: - By video: group_by=["video_id","video_title"] - Daily trend: interval="day" - By platform: group_by=["platform"] Data limited to last 90 days. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
list_player_requests accepts 10 parameters: limit, offset, country, sort_by, group_by, interval, platform, video_id, start_date_gte, start_date_lte. 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 list_player_requests: 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.
list_player_requests 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_player_requests 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_player_requests. 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_player_requests 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