invite_convoy_partner_member
Invite a partner member to the Convoy portal. This sends email and requires explicit user approval with confirm_send=true.
This record as markdown: /tools/sankahq-sanka-mcp/invite-convoy-partner-member.md
What invite_convoy_partner_member does on Sanka MCP Server
AI agents use invite_convoy_partner_member 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 invite_convoy_partner_member is rated Medium
This tool creates/initiates a new resource (a partner member invitation) and sends a notification email, which is a reversible modification. It does not execute arbitrary code, delete data, move money, or require the most severe categories. The requirement for explicit user approval (confirm_send=true) mitigates risk somewhat, but the tool remains Write-category.
From the tool's definition Tool description states it 'Invite a partner member to the Convoy portal' and 'sends email'. The action creates a new invitation record and triggers an email notification, modifying the state of the system by adding a new partner member invitation.
Attacks that exploit this kind of access
The rule that runs invite_convoy_partner_member 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 invite_convoy_partner_member, this is the rule to start with:
invite_convoy_partner_member 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 invite_convoy_partner_member call is checked against it from then on.
Questions about invite_convoy_partner_member
Invite a partner member to the Convoy portal. This sends email and requires explicit user approval with confirm_send=true. 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 invite_convoy_partner_member: 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.
invite_convoy_partner_member 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 invite_convoy_partner_member 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 invite_convoy_partner_member. 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.
invite_convoy_partner_member 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