list_zobjects
List zobjects (custom metadata instances) with optional filtering by type. Returns full API response including all custom attributes defined on the zobject type (e.g., pictures, keywords, stadium info for teams, biography for actors). Custom attributes are returned as top-level fields. Examples: ...
This record as markdown: /tools/com-zype-mcp-server/list-zobjects.md
What list_zobjects does on Zype Com
AI agents call list_zobjects 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 |
|---|---|---|---|
q | string | — | Search by keyword |
page | number | — | Page number (default: 1) |
sort | string | — | Field to sort by |
order | string | — | Sort order |
active | boolean | — | Filter by active status |
per_page | number | — | Results per page (default: 10, max: 500) |
zobject_type | string | — | Filter by zobject type title (e.g., "actor", "director", "teams") |
zobject_type_id | string | — | Filter by zobject type ID |
Parameters from the server's own tool schema.
Why list_zobjects is rated Low
Even though list_zobjects 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 list_zobjects 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_zobjects, this is the rule to start with:
list_zobjects 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_zobjects call is checked against it from then on.
Questions about list_zobjects
List zobjects (custom metadata instances) with optional filtering by type. Returns full API response including all custom attributes defined on the zobject type (e.g., pictures, keywords, stadium info for teams, biography for actors). Custom attributes are returned as top-level fields. Examples: list all actors, directors, teams. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
list_zobjects accepts 8 parameters: q, page, sort, order, active, per_page, zobject_type, zobject_type_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 list_zobjects: 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_zobjects 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_zobjects 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_zobjects. 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_zobjects 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