AI agents use push-file to create or update resources in MCP Appium Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Appium Server environment.
The tool creates or modifies files on the device by transferring them from the host system. This is a reversible write operation (files can be deleted or overwritten later). While it has potential for misuse (installing malware, overwriting critical files), it is not inherently destructive since files can be removed, making it Write rather than Destructive.
From the tool's definition Tool name 'push-file' and description 'Push a file to the device' indicates the tool transfers and writes files to a mobile device. This is a file modification operation that creates or places data on the target device.
Documented attack patterns abuse exactly the kind of access push-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 push-file:
{
"version": "1",
"default": "deny",
"tools": {
"push-file": {
"limits": [
{
"counter": "push-file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push-file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Push a file to the device. It is categorised as a Write tool in the MCP Appium Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Appium Server MCP server in PolicyLayer and add a rule for push-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.
push-file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the push-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 push-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.
push-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.