list_buy_requests

List Sanka Buy requests in the authenticated workspace with optional status filtering.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

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/sankahq-sanka-mcp/list-buy-requests.md

WHAT IT DOES

What list_buy_requests does on Sanka MCP Server

AI agents call list_buy_requests to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_buy_requests is rated Low

This tool retrieves and queries buy request data from the workspace. The action is read-only; it does not create, modify, delete, or execute any operations. Even with filtering parameters, the outcome is retrieving existing information without side effects. Confidence is high because the description clearly indicates a listing/query operation.

From the tool's definition Tool name uses 'list' verb and description states 'List Sanka Buy requests' with 'optional status filtering' — pure data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_buy_requests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_buy_requests, this is the rule to start with:

list_buy_requests Allowed

list_buy_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_buy_requests": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_buy_requests call is checked against it from then on.

FAQ

Questions about list_buy_requests

What does the list_buy_requests tool do? +

List Sanka Buy requests in the authenticated workspace with optional status filtering. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_buy_requests? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_buy_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 Sanka MCP Server. Nothing to install.

What risk level is list_buy_requests? +

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

Can I rate-limit list_buy_requests? +

Yes. Add a rate_limit block to the list_buy_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.

How do I block list_buy_requests completely? +

Set action: deny in the PolicyLayer policy for list_buy_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.

What MCP server provides list_buy_requests? +

list_buy_requests is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →