submit_buy_request · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_buy_request does on Sanka MCP Server

AI agents use submit_buy_request to create or update resources in Sanka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

WHY IT NEEDS A POLICY

Why submit_buy_request needs a policy

This tool creates a new buy request record in the system, which is a Write operation. While it operates in a financial domain (procurement/buying), it does not itself move money, execute payments, or commit financial obligations—it creates a request that may trigger approval workflows. The approval process and PO/Bill creation are separate downstream steps.

From the tool's definition Tool description states it 'Submit[s] a Sanka Buy request' which creates or modifies data (a buy request record). The description notes it 'may approve immediately or create approval requirements,' indicating it writes state to the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_buy_request Rate-limited

submit_buy_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_buy_request": {
      "limits": [
        {
          "counter": "submit_buy_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 submit_buy_request

What does the submit_buy_request tool do? +

Submit a Sanka Buy request after line offers are selected. This may approve immediately or create approval requirements; it does not create PO/Bill/checkout records by itself. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_buy_request? +

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

submit_buy_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_buy_request? +

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

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

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