AI agents call get_org_namespace 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 |
|---|---|---|---|
namespaceId | string | Yes | Namespace ID (string). Use list_namespaces to discover valid IDs. |
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 retrieves organizational namespace information and returns nested sub-namespace data. It has no side effects, does not modify any data, and does not execute operations. The blast radius of misuse is minimal—an attacker could only gain visibility into organizational structure, which is low-impact reconnaissance. No financial, destructive, or execution risks are present.
From the tool's definition Tool description states 'Get a CodeUp organization namespace by ID with nested sub-namespaces'. The verb 'Get' and the retrieval-only nature of the operation (no creation, modification, or deletion described) indicate this is a read operation.
Attacks that exploit this kind of access
Get a CodeUp organization namespace by ID with nested sub-namespaces. Use list_namespaces to discover valid namespace IDs. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_org_namespace accepts 2 parameters: namespaceId, organizationId. Required: namespaceId. 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 get_org_namespace: 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.
get_org_namespace 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_org_namespace 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_org_namespace. 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_org_namespace 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 →