discover_services
Search available services and products in the MIDAS marketplace
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/discover-services.md
What discover_services does on MIDAS Protocol
AI agents call discover_services 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 |
|---|---|---|---|
limit | number | — | |
category | string | — | |
currency | string | — |
Parameters from the server's own tool schema.
Why discover_services is rated Low
Despite being on a financial infrastructure server, this tool only searches/queries available services and products. It retrieves information without creating charges, modifying accounts, executing transactions, or committing financial obligations. The action is passive discovery, analogous to browsing a marketplace catalog.
From the tool's definition Tool description states 'Search available services and products in the MIDAS marketplace' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs discover_services 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 discover_services, this is the rule to start with:
discover_services 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 discover_services call is checked against it from then on.
Questions about discover_services
Search available services and products in the MIDAS marketplace. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.
discover_services accepts 3 parameters: limit, category, currency. 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 discover_services: 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.
discover_services 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 discover_services 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 discover_services. 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.
discover_services 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