get_settlement_by_utr

A read tool on the PineLabs Plural PG — Payment Gateway 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-settlement-by-utr.md

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

AI agents call get_settlement_by_utr 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_settlement_by_utr is rated Low

This tool retrieves settlement information without modifying data. However, settlement and financial transaction data is sensitive; unauthorized access could expose payment details, transaction history, or merchant financial information. This justifies medium severity despite being a Read operation.

From the tool's definition Tool name 'get_settlement_by_utr' indicates a retrieval/query operation (get) that fetches settlement data by Unique Transaction Reference. No destructive or write operations implied.

Questions about get_settlement_by_utr

What does the get_settlement_by_utr tool do? +

get_settlement_by_utr 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_settlement_by_utr? +

Register the PineLabs Plural PG — Payment Gateway MCP Server MCP server in PolicyLayer and add a rule for get_settlement_by_utr: 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_settlement_by_utr? +

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

Can I rate-limit get_settlement_by_utr? +

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

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

get_settlement_by_utr 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PineLabs Plural PG — Payment Gateway MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.