get_order_details
Fetch order details within a date range.
This record as markdown: /tools/io-github-plural-pinelabs-pinelabs-online-mcp/get-order-details.md
What get_order_details does on PineLabs Plural PG — Payment Gateway MCP Server
AI agents call get_order_details 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_order_details is rated Low
This is a read-only operation that retrieves order information. While classified as Read (no side effects), the severity is elevated to 'medium' rather than 'low' because order details may contain sensitive financial and personal information (customer names, amounts, payment methods, transaction IDs).
From the tool's definition Tool name is 'get_order_details' and description states 'Fetch order details within a date range.' The verb 'fetch' indicates data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs get_order_details 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_order_details, this is the rule to start with:
get_order_details 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_order_details call is checked against it from then on.
Questions about get_order_details
Fetch order details within a date range. 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_order_details: 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_order_details 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_order_details 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_order_details. 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_order_details 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