update_buy_request
Update editable draft fields on a Sanka Buy request.
This record as markdown: /tools/sankahq-sanka-mcp/update-buy-request.md
What update_buy_request does on Sanka MCP Server
AI agents use update_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 update_buy_request is rated Medium
This tool modifies existing buy request records by updating draft fields. Since it targets draft fields specifically, the changes appear reversible and not destructive. However, given the financial context (purchase/procurement operations) and the potential to alter purchase obligations before approval, this rates medium severity.
From the tool's definition Tool name 'update_buy_request' and description 'Update editable draft fields on a Sanka Buy request' indicate modification of purchase request data. The term 'update' combined with 'draft fields' shows reversible data changes.
Attacks that exploit this kind of access
The rule that runs update_buy_request 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 update_buy_request, this is the rule to start with:
update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every update_buy_request call is checked against it from then on.
Questions about update_buy_request
Update editable draft fields on a Sanka Buy request. 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.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_buy_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue