get_regions
Get available regions for workspace creation. Returns region codes and display names.
This record as markdown: /tools/dugynoo-huly-mcp/get-regions.md
What get_regions does on Huly
AI agents call get_regions to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_regions is rated Low
This is a read-only query that retrieves metadata about available regions. No data is created, modified, deleted, or used to trigger external operations. The impact is minimal — it simply provides information about where workspaces can be created, similar to listing available options. Low severity because misuse would only expose configuration details, not enable harmful actions on workspaces or data.
From the tool's definition Tool name 'get_regions' with description 'Get available regions for workspace creation. Returns region codes and display names.' — retrieves configuration data without modifying state.
Attacks that exploit this kind of access
The rule that runs get_regions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_regions, this is the rule to start with:
get_regions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every get_regions call is checked against it from then on.
Questions about get_regions
Get available regions for workspace creation. Returns region codes and display names. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_regions: 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 Huly. Nothing to install.
get_regions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_regions 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 get_regions. 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.
get_regions is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue