get_buy_request

Load one Sanka Buy request including lines, active offer selections, and merchant purchases.

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/get-buy-request.md

WHAT IT DOES

What get_buy_request does on Sanka MCP Server

AI agents call get_buy_request 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 get_buy_request is rated Low

This tool retrieves and queries existing buy request data without creating, modifying, deleting, or executing any operations. It has no side effects on the system state, making it a standard Read operation with low risk.

From the tool's definition Tool name 'get_buy_request' with description 'Load one Sanka Buy request' indicates data retrieval. The verb 'Load' and the inclusion of associated data (lines, offers, purchases) are read-only query operations with no modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_buy_request 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 get_buy_request, this is the rule to start with:

get_buy_request Allowed

get_buy_request 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": {
    "get_buy_request": {}
  }
}

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 get_buy_request call is checked against it from then on.

FAQ

Questions about get_buy_request

What does the get_buy_request tool do? +

Load one Sanka Buy request including lines, active offer selections, and merchant purchases. 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 get_buy_request? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_buy_request: 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 get_buy_request? +

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

Can I rate-limit get_buy_request? +

Yes. Add a rate_limit block to the get_buy_request 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_buy_request completely? +

Set action: deny in the PolicyLayer policy for get_buy_request. 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_buy_request? +

get_buy_request 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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