New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

upsert_project_target_preference

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.

SERVERHuly SOURCE@firfi/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/upsert-project-target-preference.md

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 upsert_project_target_preference is rated Medium

This tool creates or updates project preference records. While it can modify system configuration (which could affect project behavior), the changes are reversible and do not permanently delete data or move financial resources.

From the tool's definition Tool description states 'Create or update the low-level ProjectTargetPreference record' and 'merges SDK-open target preference props by key'.

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.

More on Huly, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.