获取当前设备所有注册唤醒的 App Schema 信息
AI agents call getAppSchemas to retrieve information from Current operating environment without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves application schema information from the device. While it is fundamentally a Read operation (querying registered app schemas), the severity is elevated to medium because knowledge of available app schemas and their awakening capabilities could be leveraged by an agent to discover and invoke sensitive applications or trigger unintended functionality.
From the tool's definition Tool name is 'getAppSchemas' and description states '获取当前设备所有注册唤醒的 App Schema 信息' (Get information about all registered App Schema that can be awakened on the current device). The verb '获取' (get/retrieve) indicates data retrieval without modification.
Attacks that exploit this kind of access
获取当前设备所有注册唤醒的 App Schema 信息. It is categorised as a Read tool in the Current operating environment MCP Server, which means it retrieves data without modifying state.
Register the Current operating environment MCP server in PolicyLayer and add a rule for getAppSchemas: 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 Current operating environment. Nothing to install.
getAppSchemas 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 getAppSchemas 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 getAppSchemas. 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.
getAppSchemas is provided by the Current operating environment MCP server (jackxuyi/env-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 →