List sourcing runs for a Sanka Buy request.
AI agents call list_buy_sourcing_runs 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.
This tool retrieves or queries sourcing run data associated with a Buy request. The 'list' operation is a standard read-only retrieval action with no side effects, reversible modifications, code execution, deletion, or financial transaction. Even in the context of a procurement/sourcing system, listing existing runs poses minimal risk if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List sourcing runs' — a query operation that retrieves data without modification.
Attacks that exploit this kind of access
List sourcing runs for a Sanka Buy request. 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 list_buy_sourcing_runs: 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.
list_buy_sourcing_runs 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 list_buy_sourcing_runs 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 list_buy_sourcing_runs. 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.
list_buy_sourcing_runs 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 →