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

get_convoy_invoice_request

Load one Convoy invoice request with submission, review, and payment evidence.

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

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

What get_convoy_invoice_request does on Sanka MCP Server

AI agents call get_convoy_invoice_request to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_convoy_invoice_request is rated Low

This tool retrieves and queries invoice request data without creating, modifying, deleting, or executing operations. It has minimal blast radius as misuse would only expose read access to invoice records. The 'get' pattern and 'Load' verb confirm retrieval semantics with no side effects.

From the tool's definition Tool name 'get_convoy_invoice_request' uses 'get' prefix; description states 'Load one Convoy invoice request' indicating data retrieval with no modification or deletion.

Questions about get_convoy_invoice_request

What does the get_convoy_invoice_request tool do? +

Load one Convoy invoice request with submission, review, and payment evidence. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_convoy_invoice_request? +

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

get_convoy_invoice_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_convoy_invoice_request? +

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

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

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