Low Risk

get-device-time

Get the current device time

How to control get-device-time ↓

AI agents call get-device-time 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.

Low Risk

This tool retrieves the current time from a device, which is a read-only query operation. It does not modify, delete, execute arbitrary code, move money, or trigger state changes. The potential for misuse is minimal, as time information is typically non-sensitive and read-only access presents no destructive or harmful capability.

From the tool's definition Tool name is 'get-device-time' and description states 'Get the current device time' — a pure retrieval operation with no side effects or data modification.

Documented attack patterns abuse exactly the kind of access get-device-time 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-device-time:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-device-time": {}
  }
}

get-device-time is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Appium Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-device-time tool do? +

Get the current device time. It is categorised as a Read tool in the MCP Appium Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-device-time? +

Register the MCP Appium Server MCP server in PolicyLayer and add a rule for get-device-time: 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.

What risk level is get-device-time? +

get-device-time is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-device-time? +

Yes. Add a rate_limit block to the get-device-time 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.

How do I block get-device-time completely? +

Set action: deny in the PolicyLayer policy for get-device-time. 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.

What MCP server provides get-device-time? +

get-device-time 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.

Enforce policy on every MCP Appium Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.