get_buy_sourcing_run

What get_buy_sourcing_run does on Sanka MCP Server

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

The tool retrieves a single sourcing run record by identifier. This is a read-only operation that queries existing data without creating, modifying, deleting, or executing any operations. Even in the context of a procurement system (evidenced by sibling tools like 'activate_invoice' and 'activate_order'), loading/fetching a record is fundamentally a read operation with minimal risk of misuse.

From the tool's definition Tool name and description indicate retrieval: 'Load one Sanka Buy sourcing run by id' - a query/fetch operation with no mutation or side effects.

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

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

Questions about get_buy_sourcing_run