cpu_count

THE RISK

Low Risk

Why cpu_count needs a policy

This tool queries device properties and returns static information (CPU core count) with no ability to modify system state, execute operations, or cause side effects. It is purely informational retrieval, matching the Read category definition.

From the tool's definition Tool name 'cpu_count' and description 'Returns the number of CPU cores on the connected Android device. No parameters are required.' indicate a read-only query operation that retrieves device information without modification or side effects.

Documented attack patterns abuse exactly the kind of access cpu_count gives an agent:

POLICY

How to control cpu_count

PolicyLayer is an MCP gateway — it sits between your AI agents and Ultimate Android MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cpu_count:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cpu_count": {}
  }
}

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

Create a free account and register Ultimate Android MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ultimate Android MCP tools

Destructive uninstall_package Uninstalls the specified package from the connected Android device. Requires the package_n Execute execute_adb_shell Executes a raw ADB shell command on the connected Android device and returns the output. R Execute launch_app Launches the app with the specified package name on the connected Android device. Requires Execute input_back Simulates a back button event on the connected Android device. No parameters are required. Execute input_home Simulates a home button event on the connected Android device. No parameters are required. Execute input_keyevent Simulates a key event with the specified keycode on the connected Android device. Requires Execute input_roll Simulates a rolling gesture with the specified dx and dy values on the connected Android d Execute input_text Simulates typing the given text input into the currently focused field on the connected An

All 35 Ultimate Android MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cpu_count

What does the cpu_count tool do? +

Returns the number of CPU cores on the connected Android device. No parameters are required. It is categorised as a Read tool in the Ultimate Android MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cpu_count? +

Register the Ultimate Android MCP server in PolicyLayer and add a rule for cpu_count: 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 Ultimate Android MCP. Nothing to install.

What risk level is cpu_count? +

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

Can I rate-limit cpu_count? +

Yes. Add a rate_limit block to the cpu_count 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 cpu_count completely? +

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

cpu_count is provided by the Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ultimate Android MCP tool call.

Start from Ultimate Android MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →