find_by_name

Find subaccounts by name (partial match).

SERVERVultr MCP SOURCErsp2k/mcp-vultr

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rsp2k-mcp-vultr/find-by-name.md

WHAT IT DOES

What find_by_name does on Vultr MCP

AI agents call find_by_name to retrieve information from Vultr MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_by_name is rated Low

This tool performs a read-only lookup operation to locate subaccounts by matching a name pattern. It returns information without creating, modifying, deleting, or executing any changes to infrastructure or data. The partial match search is a standard query pattern typical of Read category tools.

From the tool's definition Tool name 'find_by_name' and description 'Find subaccounts by name (partial match)' indicate a search/query operation that retrieves existing data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_by_name safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_by_name, this is the rule to start with:

find_by_name Allowed

find_by_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_by_name": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every find_by_name call is checked against it from then on.

FAQ

Questions about find_by_name

What does the find_by_name tool do? +

Find subaccounts by name (partial match). It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_by_name? +

Register the Vultr MCP server in PolicyLayer and add a rule for find_by_name: 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.

What risk level is find_by_name? +

find_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_by_name? +

Yes. Add a rate_limit block to the find_by_name 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.

How do I block find_by_name completely? +

Set action: deny in the PolicyLayer policy for find_by_name. 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.

What MCP server provides find_by_name? +

find_by_name 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.

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr tools →

Across the catalogue

get_cocktail_by_name on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →