New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_buy_request

Update editable draft fields on a Sanka Buy request.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about update_buy_request

What does the update_buy_request tool do? +

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.

How do I enforce a policy on update_buy_request? +

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.

What risk level is update_buy_request? +

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

Can I rate-limit update_buy_request? +

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.

How do I block update_buy_request completely? +

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.

What MCP server provides update_buy_request? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.