AI agents call list_namespaces to retrieve information from Yunxiao without modifying anything — 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 for pagination. Starts at 1. |
sort | string | — | Sort direction: asc or desc. |
search | string | — | Namespace search keyword. |
orderBy | string | — | Sort field: created_at or updated_at. |
perPage | number | — | Page size for pagination. Supports 1-100. |
parentId | number | — | Parent namespace ID. Omit to list namespaces available to the current user. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool performs a query/listing operation that retrieves organizational metadata about CodeUp namespaces. There is no creation, modification, deletion, or execution of operations. The blast radius of misuse is minimal - an unauthorized listing of namespaces could expose organizational structure but cannot modify systems or data. This is a standard read operation.
From the tool's definition Tool description explicitly states 'List CodeUp namespaces or groups' - a retrieval operation with no side effects. Lists organizational hierarchical structure without modifying data.
Attacks that exploit this kind of access
List CodeUp namespaces or groups in a Yunxiao organization. Namespaces organize repositories into hierarchical groups. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_namespaces accepts 7 parameters: page, sort, search, orderBy, perPage, parentId, organizationId. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for list_namespaces: 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 Yunxiao. Nothing to install.
list_namespaces 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_namespaces 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_namespaces. 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_namespaces is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →