list_revenue_models

List available revenue models (AVOD, SVOD, TVOD, etc.).

SERVERZype Com SOURCEzype/zype-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/list-revenue-models.md

WHAT IT DOES

What list_revenue_models does on Zype Com

AI agents call list_revenue_models 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
`page`	number	—	Page number (default: 1)
`per_page`	number	—	Results per page

Parameters from the server's own tool schema.

RISK

Why list_revenue_models is rated Low

Even though list_revenue_models 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

RECOMMENDED RULE

The rule that runs list_revenue_models 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_revenue_models, this is the rule to start with:

list_revenue_models Allowed

list_revenue_models is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_revenue_models": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every list_revenue_models call is checked against it from then on.

FAQ

Questions about list_revenue_models

What does the list_revenue_models tool do? +

List available revenue models (AVOD, SVOD, TVOD, etc.). It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.

What parameters does list_revenue_models accept? +

list_revenue_models accepts 2 parameters: page, per_page. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_revenue_models? +

Register the Zype Com MCP server in PolicyLayer and add a rule for list_revenue_models: 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.

What risk level is list_revenue_models? +

list_revenue_models is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_revenue_models? +

Yes. Add a rate_limit block to the list_revenue_models 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.

How do I block list_revenue_models completely? +

Set action: deny in the PolicyLayer policy for list_revenue_models. 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.

What MCP server provides list_revenue_models? +

list_revenue_models 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.

KEEP EXPLORING

More on Zype Com, and thousands of servers like it.

This server

All 296 Zype Com tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →