AI agents call pull-file 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/reads a file from a mobile device to the host system. It has no side effects on the device itself — it is a read/fetch operation. However, it could expose sensitive data from the device (credentials, private files, app data), warranting a medium severity rating.
From the tool's definition Pull a file from the device
Documented attack patterns abuse exactly the kind of access pull-file 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 pull-file:
{
"version": "1",
"default": "deny",
"tools": {
"pull-file": {}
}
}pull-file 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.
Pull a file from the device. 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 pull-file: 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.
pull-file 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 pull-file 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 pull-file. 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.
pull-file 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.