Low Risk

device_info

Get detailed info about a device: model, Android version, screen size, SDK level, battery level

Part of the Scrcpy MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

scrcpy-mcp Read

AI agents call device_info to retrieve information from Scrcpy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though device_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-juancf-scrcpy-mcp.yaml
tools:
  device_info:
    rules:
      - action: allow

See the full Scrcpy policy for all 38 tools.

Tool Name device_info
Category Read
MCP Server Scrcpy MCP Server
Risk Level Low

View all 38 tools →

Agents calling read-class tools like device_info have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the device_info tool do? +

Get detailed info about a device: model, Android version, screen size, SDK level, battery level. It is categorised as a Read tool in the Scrcpy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on device_info? +

Add a rule in your Intercept YAML policy under the tools section for device_info. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Scrcpy MCP server.

What risk level is device_info? +

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

Can I rate-limit device_info? +

Yes. Add a rate_limit block to the device_info rule in your Intercept 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 device_info completely? +

Set action: deny in the Intercept policy for device_info. 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 device_info? +

device_info is provided by the Scrcpy MCP server (scrcpy-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Scrcpy

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.