service_list
List all system services with their current status (running/stopped) and whether they are enabled at boot. Useful for an overview of all available services.
This record as markdown: /tools/nasbridge/service-list.md
What service_list does on Nasbridge
AI agents call service_list to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why service_list is rated Low
This is a pure read operation that queries and returns service status information. It has no side effects—it does not create, modify, delete, or execute any system changes. The blast radius of misuse is minimal since an agent can only view information, not alter system state. Low severity is appropriate for reconnaissance-only access.
From the tool's definition Tool name 'service_list' and description 'List all system services with their current status (running/stopped) and whether they are enabled at boot' indicate a query operation that retrieves service status information without modifying, deleting, or executing…
Attacks that exploit this kind of access
The rule that runs service_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For service_list, this is the rule to start with:
service_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every service_list call is checked against it from then on.
Questions about service_list
List all system services with their current status (running/stopped) and whether they are enabled at boot. Useful for an overview of all available services. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for service_list: 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 Nasbridge. Nothing to install.
service_list 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 service_list 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 service_list. 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.
service_list is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue