# configure_basic_web_lb A write tool on the Vultr MCP MCP server. Agent View of the PolicyLayer registry record for `configure_basic_web_lb`. HTML page: https://policylayer.com/tools/rsp2k-mcp-vultr/configure-basic-web-lb ## Facts - Tool: `configure_basic_web_lb` - Server: Vultr MCP (`rsp2k/mcp-vultr`) — https://policylayer.com/tools/rsp2k-mcp-vultr.md - Homepage: https://github.com/rsp2k/mcp-vultr - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "configure_basic_web_lb", "arguments": {} } } ``` ## Why configure_basic_web_lb is rated Medium Configuration of load balancer settings is a reversible write operation that creates or modifies infrastructure settings. While the tool modifies cloud infrastructure, the change is typically reversible (settings can be reconfigured). This is less severe than destructive operations (which cannot be undone) or execute operations (which run arbitrary code). From the tool's own definition: "Tool name 'configure_basic_web_lb' indicates configuration of a web load balancer. The 'configure' verb suggests modifying settings or parameters of an existing load balancer resource. Description is empty, limiting confidence." ## Use case AI agents use configure_basic_web_lb 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Vultr MCP: ```json { "version": "1", "default": "deny", "tools": { "configure_basic_web_lb": { "limits": [ { "counter": "configure_basic_web_lb_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Vultr MCP (283) - `delete` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete.md - `delete_bare_metal_server` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-bare-metal-server.md - `delete_cdn_ssl_certificate` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-cdn-ssl-certificate.md - `delete_cdn_zone` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-cdn-zone.md - `delete_collection` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-collection.md - `delete_connection_pool` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-connection-pool.md - `delete_dns_domain` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-dns-domain.md - `delete_dns_record` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-dns-record.md - `delete_domain` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-domain.md - `delete_export` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-export.md - `delete_forwarding_rule` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-forwarding-rule.md - `delete_group` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-group.md - `delete_ipv4` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-ipv4.md - `delete_iso` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-iso.md - `delete_kafka_topic` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-kafka-topic.md - `delete_kubernetes_cluster` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-kubernetes-cluster.md - `delete_kubernetes_cluster_with_resources` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-kubernetes-cluster-with-resources.md - `delete_kubernetes_node` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-kubernetes-node.md - `delete_kubernetes_node_pool` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-kubernetes-node-pool.md - `delete_logical_database` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-logical-database.md - `delete_record` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-record.md - `delete_rule` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-rule.md - `delete_serverless_inference` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-serverless-inference.md - `delete_ssl` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-ssl.md - `delete_startup_script` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-startup-script.md - `delete_user` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-user.md - `delete_vpc2` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/delete-vpc2.md - `purge_cdn_zone` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/purge-cdn-zone.md - `remove_ip_whitelist_entry` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/remove-ip-whitelist-entry.md - `remove_resource_from_collection` — Destructive — https://policylayer.com/tools/rsp2k-mcp-vultr/remove-resource-from-collection.md - …and 253 more: https://policylayer.com/tools/rsp2k-mcp-vultr.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=rsp2k-mcp-vultr · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/rsp2k-mcp-vultr