AI agents use add_export to create or update resources in Vultr MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vultr MCP environment.
The 'add_export' tool most likely creates or writes an export configuration (e.g., exporting data, logs, or metrics from a Vultr service). Based on the sibling tools (add_ip_whitelist_entry, add_resource_to_collection), the 'add_' prefix indicates a write operation that creates or modifies a resource. Without a description, confidence is moderate.
From the tool's definition Tool name 'add_export' suggests creating or adding an export; description is empty, limiting direct evidence.
Documented attack patterns abuse exactly the kind of access add_export gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_export:
{
"version": "1",
"default": "deny",
"tools": {
"add_export": {
"limits": [
{
"counter": "add_export_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_export 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.
Free to start. No card required.
add_export. It is categorised as a Write tool in the Vultr MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vultr MCP server in PolicyLayer and add a rule for add_export: 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 Vultr MCP. Nothing to install.
add_export 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 add_export 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 add_export. 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.
add_export is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.