get_processes_by_category

WHAT IT DOES

What get_processes_by_category does on MacOS Resource Monitor MCP Server

AI agents call get_processes_by_category to retrieve information from MacOS Resource Monitor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_processes_by_category needs a policy

This tool retrieves and filters process information by category without modifying system state. It has no side effects beyond querying local system data. Confidence is moderate (0.75) rather than high due to empty tool description; if it unexpectedly executes processes rather than listing them, the classification could shift to Execute, but the naming and server context strongly suggest read-only retrieval.

From the tool's definition Tool name 'get_processes_by_category' indicates a retrieval operation. Server description states tools are for 'identifying resource-intensive processes' and 'detailed process filtering', all read operations.

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

POLICY

How to control get_processes_by_category

PolicyLayer is an MCP gateway — it sits between your AI agents and MacOS Resource Monitor MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_processes_by_category:

policy.json

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

get_processes_by_category 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 MacOS Resource Monitor MCP Server — 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 MacOS Resource Monitor MCP Server tools

Read get_resource_intensive_processes Identify resource-intensive processes on macOS across CPU, memory, and network. Read get_system_overview get_system_overview

All 3 MacOS Resource Monitor MCP Server 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 get_processes_by_category

What does the get_processes_by_category tool do? +

get_processes_by_category. It is categorised as a Read tool in the MacOS Resource Monitor MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_processes_by_category? +

Register the MacOS Resource Monitor MCP Server MCP server in PolicyLayer and add a rule for get_processes_by_category: 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 MacOS Resource Monitor MCP Server. Nothing to install.

What risk level is get_processes_by_category? +

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

Can I rate-limit get_processes_by_category? +

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

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

get_processes_by_category is provided by the MacOS Resource Monitor MCP Server MCP server (pratyay/mac-monitor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MacOS Resource Monitor MCP Server tool call.

Start from MacOS Resource Monitor MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

3 MacOS Resource Monitor MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.