List top running processes by CPU or memory usage.
AI agents call list_processes to retrieve information from Synology MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about running processes on the NAS system. It performs a read-only query of system state with no side effects, no code execution capability, and no ability to modify, delete, or move data. The worst-case misuse scenario would be information disclosure about what processes are running, which is low-severity. No data is created, modified, or destroyed.
From the tool's definition Tool name is 'list_processes' and description states it 'List[s] top running processes by CPU or memory usage' — a pure query operation with no modification, deletion, execution, or financial impact.
Attacks that exploit this kind of access
List top running processes by CPU or memory usage. It is categorised as a Read tool in the Synology MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Synology MCP Server MCP server in PolicyLayer and add a rule for list_processes: 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 Synology MCP Server. Nothing to install.
list_processes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_processes 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.
Set action: deny in the PolicyLayer policy for list_processes. 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.
list_processes is provided by the Synology MCP Server MCP server (rafalr100/synology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →