AI agents call get_user 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 |
|---|---|---|---|
idOrUsername | string | Yes | User ID (numeric) or login username. Use list_users to discover valid values. |
Parameters from the server's own tool schema.
This tool queries and returns user information by identifier. It performs a read-only lookup operation without creating, modifying, deleting, or executing any actions. The retrieval of user metadata poses minimal risk as a standalone operation.
From the tool's definition Tool description states 'Get a Yunxiao user by ID or username' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a Yunxiao user by ID or username. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_user accepts 1 parameter: idOrUsername. Required: idOrUsername. 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_user: 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_user 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_user 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_user. 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_user 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 →