create_component · Huly MCP: Risk & Policy

WHAT IT DOES

What create_component does on Huly

AI agents use create_component to create or update resources in Huly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.

WHY IT NEEDS A POLICY

Why create_component needs a policy

An AI agent can call create_component faster than any human can review — one bad instruction and it creates or modifies resources in Huly by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_component Rate-limited

create_component stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_component": {
      "limits": [
        {
          "counter": "create_component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Huly, so you can run agents against it safely.

FAQ

Questions about create_component

What does the create_component tool do? +

Create a new component in a Huly project. Components help organize issues by area/feature. Returns the created component ID and label. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_component? +

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

create_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_component? +

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

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

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