根据企微用户电话号码 telphone 获取企微用户id userid 信息
AI agents call get_userid_by_telphone to retrieve information from MCP-YNU FastMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup operation that retrieves user ID information from what appears to be a corporate WeChat (企微) system based on a phone number query. It is purely informational with no ability to modify, delete, or execute arbitrary operations.
From the tool's definition Tool description indicates it 'gets' (获取) userid information based on a telephone number. The verb 'get' and the retrieval-only nature of looking up a user ID by phone number demonstrates no modification or side effects.
Attacks that exploit this kind of access
根据企微用户电话号码 telphone 获取企微用户id userid 信息. It is categorised as a Read tool in the MCP-YNU FastMCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP-YNU FastMCP Server MCP server in PolicyLayer and add a rule for get_userid_by_telphone: 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 MCP-YNU FastMCP Server. Nothing to install.
get_userid_by_telphone 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_userid_by_telphone 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_userid_by_telphone. 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_userid_by_telphone is provided by the MCP-YNU FastMCP Server MCP server (ynu/mcp-ynu). 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 →