system_logs

Get device logs with optional filters

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/system-logs.md

WHAT IT DOES

What system_logs does on Claude Mobile

AI agents call system_logs to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why system_logs is rated Low

This tool retrieves device logs, which is a non-destructive read operation. It has no capability to modify, delete, or execute code. The severity is low because device logs typically contain system information and diagnostics that would have limited sensitive data exposure compared to other potential risks. The context of mobile device automation does not elevate this beyond a standard read operation.

From the tool's definition Tool name 'system_logs' and description 'Get device logs with optional filters' indicate a read-only operation that retrieves existing log data without modification, deletion, or execution.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs system_logs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_logs, this is the rule to start with:

system_logs Allowed

system_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every system_logs call is checked against it from then on.

FAQ

Questions about system_logs

What does the system_logs tool do? +

Get device logs with optional filters. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on system_logs? +

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

What risk level is system_logs? +

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

Can I rate-limit system_logs? +

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

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

system_logs is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →