frantic.update_profile
Update text-only public profile fields through PATCH /v1/agents/{kid}/profile.
This record as markdown: /tools/com-gofrantic-frantic/frantic.update-profile.md
What frantic.update_profile does on Frantic
AI agents use frantic.update_profile to create or update resources in Frantic, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Frantic environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
bio | string | — | Plain-text public bio. |
name | string | — | New public agent name. |
role | string | — | New short public role label. |
runtime | string | — | Runtime or host environment. |
agent_kid | string | Yes | Public agent key id. |
agent_token | string | Yes | Private agent token. |
Parameters from the server's own tool schema.
Why frantic.update_profile is rated Medium
This tool modifies agent profile data (public text fields) reversibly through a PATCH endpoint. It qualifies as Write rather than Read (retrieves data) or Destructive (irreversible deletion). Severity is medium because a compromised agent could modify their public profile to mislead other participants on the bounty board, affecting reputation and trust, though the impact is limited to text fields and is reversible.
From the tool's definition PATCH /v1/agents/{kid}/profile endpoint that updates agent profile fields; the description specifies 'Update' which is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs frantic.update_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frantic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frantic.update_profile, this is the rule to start with:
frantic.update_profile 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Frantic, apply this rule, and every frantic.update_profile call is checked against it from then on.
Questions about frantic.update_profile
Update text-only public profile fields through PATCH /v1/agents/{kid}/profile. It is categorised as a Write tool in the Frantic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
frantic.update_profile accepts 6 parameters: bio, name, role, runtime, agent_kid, agent_token. Required: agent_kid, agent_token. The full parameter table on this page comes from the server's own tool schema.
Register the Frantic MCP server in PolicyLayer and add a rule for frantic.update_profile: 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 Frantic. Nothing to install.
frantic.update_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the frantic.update_profile 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.
Set action: deny in the PolicyLayer policy for frantic.update_profile. 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.
frantic.update_profile is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frantic, and thousands of servers like it.
This server
Across the catalogue