update_person

Update fields on an existing person. Only provided fields are modified.

SERVERHuly SOURCEdugynoo/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/dugynoo-huly-mcp/update-person.md

WHAT IT DOES

What update_person does on Huly

AI agents use update_person 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.

RISK

Why update_person is rated Medium

This tool modifies person records (likely employee/contact data) but does not delete or irreversibly destroy data. The operation is reversible—updated fields can be changed again. While it affects potentially sensitive personal information (warranting medium severity), it lacks the irreversibility of Destructive actions or the autonomous code execution risk of Execute. It is categorized as Write.

From the tool's definition Tool name 'update_person' and description 'Update fields on an existing person. Only provided fields are modified' indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_person Rate-limited

update_person 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": {
    "update_person": {
      "limits": [
        {
          "counter": "update_person_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_person

What does the update_person tool do? +

Update fields on an existing person. Only provided fields are modified. 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 update_person? +

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

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

Can I rate-limit update_person? +

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

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

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

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →