service_get

Get details of a specific service by its numeric ID, including its running state and boot-time enable status.

SERVERNasbridge SOURCEmaverick0628/nasbridge

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/nasbridge/service-get.md

WHAT IT DOES

What service_get does on Nasbridge

AI agents call service_get 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.

RISK

Why service_get is rated Low

This tool retrieves service information (running state and boot settings) without creating, modifying, or deleting anything. It is a pure query operation that has no side effects on the TrueNAS system. The low severity reflects minimal risk even if an agent queries service details, as this provides only informational output.

From the tool's definition Tool description states 'Get details of a specific service by its numeric ID, including its running state and boot-time enable status.' The verb 'Get' and the context of retrieving service metadata indicate a read-only operation with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs service_get 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_get, this is the rule to start with:

service_get Allowed

service_get 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": {
    "service_get": {}
  }
}

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

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

FAQ

Questions about service_get

What does the service_get tool do? +

Get details of a specific service by its numeric ID, including its running state and boot-time enable status. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on service_get? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for service_get: 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.

What risk level is service_get? +

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

Can I rate-limit service_get? +

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

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

service_get 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.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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