get_process

Get one Huly Process workflow definition by process ID or exact display name. If a name is ambiguous, the tool returns a typed error with candidate IDs instead of guessing.

SERVERHuly SOURCE@firfi/huly-mcp

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/io-github-dearlordylord-huly-mcp/get-process.md

WHAT IT DOES

What get_process does on Huly

AI agents call get_process 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.

RISK

Why get_process is rated Low

This tool retrieves workflow process definitions from Huly without creating, modifying, deleting, or executing any operations. It queries and returns data (a process definition) based on lookup parameters. The mechanism returns typed errors for ambiguous matches rather than taking action, confirming it is a pure read operation with no side effects.

From the tool's definition Tool description states 'Get one Huly Process workflow definition by process ID or exact display name', using 'Get' which indicates retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_process 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_process, this is the rule to start with:

get_process Allowed

get_process 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": {
    "get_process": {}
  }
}

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

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

FAQ

Questions about get_process

What does the get_process tool do? +

Get one Huly Process workflow definition by process ID or exact display name. If a name is ambiguous, the tool returns a typed error with candidate IDs instead of guessing. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_process? +

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

What risk level is get_process? +

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

Can I rate-limit get_process? +

Yes. Add a rate_limit block to the get_process 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 get_process completely? +

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

get_process is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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