get_buy_merchant_purchase
Load one Sanka Buy merchant purchase, including linked Company, Purchase Order, checkout, external order, and Bill ids when present.
This record as markdown: /tools/sankahq-sanka-mcp/get-buy-merchant-purchase.md
What get_buy_merchant_purchase does on Sanka MCP Server
AI agents call get_buy_merchant_purchase 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.
Why get_buy_merchant_purchase is rated Low
This tool retrieves and queries existing purchase data without creating, modifying, or deleting records. It returns linked identifiers and purchase information for read-only access. The low severity reflects minimal blast radius—an AI agent misusing this would only retrieve existing data, not alter business operations or finances.
From the tool's definition Tool name contains 'get_' and description states 'Load one Sanka Buy merchant purchase' with 'including linked Company, Purchase Order, checkout, external order, and Bill ids when present.' The verb 'Load' and structure indicates data retrieval with no…
Attacks that exploit this kind of access
The rule that runs get_buy_merchant_purchase 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_merchant_purchase, this is the rule to start with:
get_buy_merchant_purchase 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 Sanka MCP Server, apply this rule, and every get_buy_merchant_purchase call is checked against it from then on.
Questions about get_buy_merchant_purchase
Load one Sanka Buy merchant purchase, including linked Company, Purchase Order, checkout, external order, and Bill ids when present. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_buy_merchant_purchase: 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.
get_buy_merchant_purchase 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_buy_merchant_purchase 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_buy_merchant_purchase. 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_buy_merchant_purchase 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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue