list_purchase_requests
List purchase requests loaded from CSV and created during this server run.
This record as markdown: /tools/nitrostack/list-purchase-requests.md
What list_purchase_requests does on Nitrostack
AI agents call list_purchase_requests to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_purchase_requests is rated Low
Tool retrieves and lists purchase request data without modifying, deleting, or executing operations.
From the tool's definition List purchase requests loaded from CSV and created during this server run.
Attacks that exploit this kind of access
The rule that runs list_purchase_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_purchase_requests, this is the rule to start with:
list_purchase_requests 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 Nitrostack, apply this rule, and every list_purchase_requests call is checked against it from then on.
Questions about list_purchase_requests
List purchase requests loaded from CSV and created during this server run. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.
Register the Nitrostack MCP server in PolicyLayer and add a rule for list_purchase_requests: 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 Nitrostack. Nothing to install.
list_purchase_requests 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 list_purchase_requests 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 list_purchase_requests. 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.
list_purchase_requests is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue