pay_discover
Search for paid API services that accept USDC payments.\n\n
This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-discover.md
What pay_discover does on Pay Mcp
AI agents call pay_discover to retrieve information from Pay Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pay_discover is rated Low
pay_discover searches for paid API services that accept USDC payments. Despite being on a financial server, the tool itself only retrieves/queries information about available services. It does not initiate payments, move funds, or modify any state. The financial context of sibling tools does not elevate this read-only search operation.
From the tool's definition 'Search for paid API services' — this is a discovery/search operation with no side effects
Attacks that exploit this kind of access
The rule that runs pay_discover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pay Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_discover, this is the rule to start with:
pay_discover 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 Pay Mcp, apply this rule, and every pay_discover call is checked against it from then on.
Questions about pay_discover
Search for paid API services that accept USDC payments.\n\n. It is categorised as a Read tool in the Pay Mcp MCP Server, which means it retrieves data without modifying state.
Register the Pay MCP server in PolicyLayer and add a rule for pay_discover: 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 Pay Mcp. Nothing to install.
pay_discover 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 pay_discover 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 pay_discover. 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.
pay_discover is provided by the Pay MCP server (@pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pay, and thousands of servers like it.
This server
Across the catalogue