Upgrade a Linode to use the new interfaces
AI agents invoke upgrade_linode_interfaces to trigger actions in Linode MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Upgrading a Linode's network interfaces is an operational change that reconfigures live infrastructure. It is not a simple write (create/update of a record) but rather triggers an execution of a migration or upgrade process on a running or stopped instance.
From the tool's definition 'Upgrade a Linode to use the new interfaces' — triggers a system-level upgrade operation on a cloud compute instance
Documented attack patterns abuse exactly the kind of access upgrade_linode_interfaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upgrade_linode_interfaces:
{
"version": "1",
"default": "deny",
"tools": {
"upgrade_linode_interfaces": {
"limits": [
{
"counter": "upgrade_linode_interfaces_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} upgrade_linode_interfaces stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upgrade a Linode to use the new interfaces. It is categorised as a Execute tool in the Linode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for upgrade_linode_interfaces: 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 Linode MCP Server. Nothing to install.
upgrade_linode_interfaces is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upgrade_linode_interfaces 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 upgrade_linode_interfaces. 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.
upgrade_linode_interfaces is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linode MCP Server, 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.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.