upsert_project_target_preference · Huly MCP: Risk & Policy

WHAT IT DOES

What upsert_project_target_preference does on Huly

AI agents use upsert_project_target_preference 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 upsert_project_target_preference needs a policy

An AI agent can call upsert_project_target_preference 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

upsert_project_target_preference Rate-limited

upsert_project_target_preference 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": {
    "upsert_project_target_preference": {
      "limits": [
        {
          "counter": "upsert_project_target_preference_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 upsert_project_target_preference

What does the upsert_project_target_preference tool do? +

Create or update the low-level ProjectTargetPreference record for a project. This refreshes usedOn and merges SDK-open target preference props by key. Use for tracker SDK parity or advanced administration; ordinary project and issue workflows usually do not need this tool. 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 upsert_project_target_preference? +

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

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

Can I rate-limit upsert_project_target_preference? +

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

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

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