get_service
Get details of a specific service
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/get-service.md
What get_service does on MIDAS Protocol
AI agents call get_service to retrieve information from MIDAS Protocol without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
serviceId | string | Yes |
Parameters from the server's own tool schema.
Why get_service is rated Low
This tool retrieves information about a service without creating, modifying, deleting, or executing anything. It has no side effects and does not commit financial obligations. Although it operates within a financial infrastructure system (MIDAS Protocol), the tool itself merely queries service metadata.
From the tool's definition Tool name 'get_service' with description 'Get details of a specific service' indicates a retrieval operation. The verb 'Get' and the read-only nature of fetching service details align with the Read category.
Attacks that exploit this kind of access
The rule that runs get_service safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_service, this is the rule to start with:
get_service 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 MIDAS Protocol, apply this rule, and every get_service call is checked against it from then on.
Questions about get_service
Get details of a specific service. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.
get_service accepts 1 parameter: serviceId. Required: serviceId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for get_service: 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 MIDAS Protocol. Nothing to install.
get_service 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 get_service 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 get_service. 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.
get_service is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue