get_merchant_success_rate

A read tool on the PineLabs Plural PG — Payment Gateway MCP server.

SERVERPineLabs Plural PG — Payment Gateway MCP Server SOURCEpypi:pinelabs-mcp-server

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-plural-pinelabs-pinelabs-online-mcp/get-merchant-success-rate.md

WHAT IT DOES

What get_merchant_success_rate does on PineLabs Plural PG — Payment Gateway MCP Server

AI agents call get_merchant_success_rate to retrieve information from PineLabs Plural PG — Payment Gateway MCP Server 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_merchant_success_rate is rated Low

This tool retrieves/queries merchant success rate data without modifying, deleting, or committing financial transactions. It has no destructive or irreversible effects. The sibling tools on this server (cancel_order, capture_order, create_order, etc.) perform write/financial actions, but this tool's name indicates a read-only operation.

From the tool's definition Tool name 'get_merchant_success_rate' indicates retrieval of merchant performance metrics with no side effects. The 'get_' prefix is a standard pattern for read-only queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_merchant_success_rate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and PineLabs Plural PG — Payment Gateway MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_merchant_success_rate, this is the rule to start with:

get_merchant_success_rate Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect PineLabs Plural PG — Payment Gateway MCP Server, apply this rule, and every get_merchant_success_rate call is checked against it from then on.

FAQ

Questions about get_merchant_success_rate

What does the get_merchant_success_rate tool do? +

get_merchant_success_rate is a read tool on the PineLabs Plural PG — Payment Gateway MCP Server MCP server. It is categorised as a Read tool in the PineLabs Plural PG — Payment Gateway MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_merchant_success_rate? +

Register the PineLabs Plural PG — Payment Gateway MCP Server MCP server in PolicyLayer and add a rule for get_merchant_success_rate: 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 PineLabs Plural PG — Payment Gateway MCP Server. Nothing to install.

What risk level is get_merchant_success_rate? +

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

Can I rate-limit get_merchant_success_rate? +

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

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

get_merchant_success_rate is provided by the PineLabs Plural PG — Payment Gateway MCP Server MCP server (pypi:pinelabs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on PineLabs Plural PG — Payment Gateway MCP Server, and thousands of servers like it.

This server

All 57 PineLabs Plural PG — Payment Gateway MCP Server 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 →