archive_convoy_partner
Archive a Convoy partner after explicit approval. This preserves history and does not delete the linked Sanka company.
This record as markdown: /tools/sankahq-sanka-mcp/archive-convoy-partner.md
What archive_convoy_partner does on Sanka MCP Server
AI agents use archive_convoy_partner 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 archive_convoy_partner is rated Medium
Archiving is typically a reversible Write operation that changes data state without permanent deletion. The description explicitly states it 'does not delete', confirming this is not Destructive. While it requires 'explicit approval', the operation itself modifies partner records rather than executing arbitrary code or reading data.
From the tool's definition Archive operation that 'preserves history and does not delete' indicates reversible data modification rather than irreversible deletion. The tool modifies the status/state of a Convoy partner record.
Attacks that exploit this kind of access
The rule that runs archive_convoy_partner 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 archive_convoy_partner, this is the rule to start with:
archive_convoy_partner 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 archive_convoy_partner call is checked against it from then on.
Questions about archive_convoy_partner
Archive a Convoy partner after explicit approval. This preserves history and does not delete the linked Sanka company. 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 archive_convoy_partner: 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.
archive_convoy_partner 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 archive_convoy_partner 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 archive_convoy_partner. 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.
archive_convoy_partner 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