Get all available contexts (NATIVE_APP, WEBVIEW, etc.)
AI agents call get-contexts to retrieve information from MCP Appium Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available contexts in an Appium session. It performs no side effects, executes no code, modifies no data, and poses minimal risk. The information retrieved (context names) is read-only state information. While knowledge of available contexts could theoretically inform subsequent malicious actions, the tool itself is purely informational.
From the tool's definition Tool name 'get-contexts' and description 'Get all available contexts (NATIVE_APP, WEBVIEW, etc.)' indicate a retrieval operation that queries available execution contexts without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access get-contexts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Appium Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-contexts:
{
"version": "1",
"default": "deny",
"tools": {
"get-contexts": {}
}
}get-contexts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all available contexts (NATIVE_APP, WEBVIEW, etc.). It is categorised as a Read tool in the MCP Appium Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Appium Server MCP server in PolicyLayer and add a rule for get-contexts: 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 Appium Server. Nothing to install.
get-contexts 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-contexts 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-contexts. 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-contexts is provided by the MCP Appium Server MCP server (rahulec08/appium-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 110 MCP Appium Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
110 MCP Appium Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.