get_order_details

Fetch order details within a date range.

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

Questions about get_order_details

What does the get_order_details tool do? +

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.

How do I enforce a policy on get_order_details? +

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.

What risk level is get_order_details? +

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

Can I rate-limit get_order_details? +

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.

How do I block get_order_details completely? +

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.

What MCP server provides get_order_details? +

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.

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