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

review_convoy_invoice_request

Approve, reject, cancel, or mark a Convoy invoice request paid. Requires explicit approval with confirm=true. Marking paid records evidence only; it does not execute a bank transfer.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/review-convoy-invoice-request.md

What review_convoy_invoice_request does on Sanka MCP Server

AI agents call review_convoy_invoice_request to permanently remove resources in Sanka MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why review_convoy_invoice_request is rated Critical

An AI agent that decides to call review_convoy_invoice_request doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Sanka MCP Server is gone. There is no undo for destructive operations.

Questions about review_convoy_invoice_request

What does the review_convoy_invoice_request tool do? +

Approve, reject, cancel, or mark a Convoy invoice request paid. Requires explicit approval with confirm=true. Marking paid records evidence only; it does not execute a bank transfer. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on review_convoy_invoice_request? +

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

review_convoy_invoice_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit review_convoy_invoice_request? +

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

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

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