agent_studio_update_agent_metadata

Update Agent Metadata

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/agent-studio-update-agent-metadata.md

WHAT IT DOES

What agent_studio_update_agent_metadata does on Ghl

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

Parameter	Type	Required	Description
`name`	string	—	Name of the agent
`source`	string	—
`status`	string	—	Status of the agent
`agentId`	string	Yes
`locationId`	string	—	Location ID for authorization (cannot be updated) Defaults to GHL_LOCATION_ID when omitted.
`description`	string	—	Description of the agent

Parameters from the server's own tool schema.

RISK

Why agent_studio_update_agent_metadata is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_studio_update_agent_metadata safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_studio_update_agent_metadata, this is the rule to start with:

agent_studio_update_agent_metadata Rate-limited

agent_studio_update_agent_metadata 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": {
    "agent_studio_update_agent_metadata": {
      "limits": [
        {
          "counter": "agent_studio_update_agent_metadata_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 Ghl, apply this rule, and every agent_studio_update_agent_metadata call is checked against it from then on.

FAQ

Questions about agent_studio_update_agent_metadata

What does the agent_studio_update_agent_metadata tool do? +

Update Agent Metadata. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does agent_studio_update_agent_metadata accept? +

agent_studio_update_agent_metadata accepts 6 parameters: name, source, status, agentId, locationId, description. Required: agentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agent_studio_update_agent_metadata? +

Register the Ghl MCP server in PolicyLayer and add a rule for agent_studio_update_agent_metadata: 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 Ghl. Nothing to install.

What risk level is agent_studio_update_agent_metadata? +

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

Can I rate-limit agent_studio_update_agent_metadata? +

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

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

agent_studio_update_agent_metadata is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

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

Guides

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