source_buy_request · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What source_buy_request does on Sanka MCP Server

AI agents invoke source_buy_request to trigger actions in Sanka MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why source_buy_request needs a policy

This tool executes a sourcing operation against an external system (Shopify Global Catalog). While it doesn't directly modify persistent data in the primary system (making it not Write or Destructive), it triggers an external process that interacts with third-party infrastructure. The results may be queued or unavailable, indicating asynchronous execution of a real operation.

From the tool's definition Tool description states it will 'Start or record a sourcing run' which initiates an external operation with Shopify Global Catalog. The action triggers a process whose effects depend on the specific buy request arguments provided and the provider's response.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

source_buy_request Rate-limited

source_buy_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "source_buy_request": {
      "limits": [
        {
          "counter": "source_buy_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about source_buy_request

What does the source_buy_request tool do? +

Start or record a sourcing run for a Sanka Buy request. MVP provider is Shopify Global Catalog; provider results may be queued or unavailable until the adapter is configured. It is categorised as a Execute tool in the Sanka MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on source_buy_request? +

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

source_buy_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit source_buy_request? +

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

Set action: deny in the PolicyLayer policy for source_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 source_buy_request? +

source_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.