AI agents call get_phone_info to retrieve information from Lkx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data lookup tool that retrieves publicly available information about phone specifications. It performs read-only operations with no ability to modify, delete, or execute arbitrary code. The tool has minimal blast radius if misused by an AI agent, as it only returns informational data about phone models.
From the tool's definition Tool description states it queries detailed information about phone models including brand, release date, screen, processor, battery and other parameters. The verb '查询' (query) indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
查询手机型号的详细信息，包括品牌、发布日期、屏幕、处理器、电池等参数. It is categorised as a Read tool in the Lkx MCP Server, which means it retrieves data without modifying state.
Register the Lkx MCP server in PolicyLayer and add a rule for get_phone_info: 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 Lkx. Nothing to install.
get_phone_info 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_phone_info 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_phone_info. 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_phone_info is provided by the Lkx MCP server (liukexina/lkx-mcp). 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 →