get_settlement_by_utr
A read tool on the PineLabs Plural PG — Payment Gateway MCP server.
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.
Attacks that exploit this kind of access
The rule that runs get_settlement_by_utr 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_settlement_by_utr, this is the rule to start with:
get_settlement_by_utr 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_settlement_by_utr call is checked against it from then on.
Questions about get_settlement_by_utr
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.
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.
get_settlement_by_utr 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_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.
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.
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.
Across the catalogue