get_payment_link_by_merchant_reference
Get a payment link by merchant reference.
This record as markdown: /tools/io-github-plural-pinelabs-pinelabs-online-mcp/get-payment-link-by-merchant-reference.md
What get_payment_link_by_merchant_reference does on PineLabs Plural PG — Payment Gateway MCP Server
AI agents call get_payment_link_by_merchant_reference 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.
Why get_payment_link_by_merchant_reference is rated Low
This tool queries and retrieves an existing payment link using a merchant reference identifier. It performs a read-only lookup with no side effects, no data modification, and no financial transaction execution. Although it relates to payments, it merely fetches metadata about an existing payment link rather than creating, modifying, or processing a payment.
From the tool's definition Tool name includes 'get', and description states 'Get a payment link by merchant reference' — a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs get_payment_link_by_merchant_reference 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_payment_link_by_merchant_reference, this is the rule to start with:
get_payment_link_by_merchant_reference 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 PineLabs Plural PG — Payment Gateway MCP Server, apply this rule, and every get_payment_link_by_merchant_reference call is checked against it from then on.
Questions about get_payment_link_by_merchant_reference
Get a payment link by merchant reference. 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.
Register the PineLabs Plural PG — Payment Gateway MCP Server MCP server in PolicyLayer and add a rule for get_payment_link_by_merchant_reference: 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.
get_payment_link_by_merchant_reference 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_payment_link_by_merchant_reference 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_payment_link_by_merchant_reference. 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_payment_link_by_merchant_reference 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.
More on PineLabs Plural PG — Payment Gateway MCP Server, and thousands of servers like it.
Across the catalogue