create_convoy_invoice_request
Create one monthly invoice request for a partner. Active partner members may receive an email, so explicit approval with confirm_send=true is required.
This record as markdown: /tools/sankahq-sanka-mcp/create-convoy-invoice-request.md
What create_convoy_invoice_request does on Sanka MCP Server
AI agents use create_convoy_invoice_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 create_convoy_invoice_request is rated Medium
This tool creates and modifies invoice request records rather than deleting or financial transaction execution. While it triggers email notifications and involves financial workflow processes, the core action is Write (create/modify) rather than Financial (move money) or Destructive (delete). The reversible nature and data creation pattern classify it as Write.
From the tool's definition Tool description states "Create one monthly invoice request" — a clear create operation that modifies data by generating a new invoice request record.
Attacks that exploit this kind of access
The rule that runs create_convoy_invoice_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 create_convoy_invoice_request, this is the rule to start with:
create_convoy_invoice_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 create_convoy_invoice_request call is checked against it from then on.
Questions about create_convoy_invoice_request
Create one monthly invoice request for a partner. Active partner members may receive an email, so explicit approval with confirm_send=true is required. 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 create_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.
create_convoy_invoice_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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
This server
Across the catalogue