get_service_info

Get detailed information about a specific service — capabilities, endpoints, and required credentials.

SERVER0nmcp SOURCE0nmcp

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/io-github-0nork-0nmcp/get-service-info.md

WHAT IT DOES

What get_service_info does on 0nmcp

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

RISK

Why get_service_info is rated Low

This tool queries and returns metadata about services (capabilities, endpoints, credentials info) without modifying state, executing code, or triggering side effects. It is a straightforward informational retrieval operation, classified as Read with low severity since it only exposes service metadata that would typically be discoverable through normal API documentation channels.

From the tool's definition Tool name 'get_service_info' and description 'Get detailed information about a specific service' indicate a retrieval operation with no data modification or execution of external logic.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_service_info safely

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

get_service_info Allowed

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

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

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

FAQ

Questions about get_service_info

What does the get_service_info tool do? +

Get detailed information about a specific service — capabilities, endpoints, and required credentials. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_service_info? +

Register the 0n MCP server in PolicyLayer and add a rule for get_service_info: 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 0nmcp. Nothing to install.

What risk level is get_service_info? +

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

Can I rate-limit get_service_info? +

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

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

get_service_info is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n 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 →