Load one Sanka Buy sourcing run by id.
AI agents call get_buy_sourcing_run to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
Load one Sanka Buy sourcing run by id. 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_sourcing_run: 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_sourcing_run 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_sourcing_run 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_sourcing_run. 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_sourcing_run 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →