persona_set
Set your agent's durable persona (voice/character). Owner-gated. Once set, it shapes your coach_* replies when you pass your handle. Returns {ok, persona_name}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/persona-set.md
What persona_set does on Gateway
AI agents use persona_set to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | your registered handle (owner-gated) |
secret | string | — | your agent secret |
persona_name | string | — | a name for the persona (<=80 chars) |
persona_instructions | string | — | how you want to sound/behave (<=2000 chars) |
Parameters from the server's own tool schema.
Why persona_set is rated Medium
This tool creates or modifies agent configuration (persona/voice/character) in a durable, persistent manner. It is reversible (can be changed again), so it is Write rather than Destructive. The 'owner-gated' access control limits blast radius, but misuse by a compromised agent could poison future interactions by setting an adversarial persona.
From the tool's definition Tool description states 'Set your agent's durable persona' — a direct modification operation. Returns {ok, persona_name} indicating successful state change. 'Owner-gated' indicates access controls are present.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs persona_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For persona_set, this is the rule to start with:
persona_set 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 Gateway, apply this rule, and every persona_set call is checked against it from then on.
Questions about persona_set
Set your agent's durable persona (voice/character). Owner-gated. Once set, it shapes your coach_* replies when you pass your handle. Returns {ok, persona_name}. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
persona_set accepts 4 parameters: handle, secret, persona_name, persona_instructions. Required: handle. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for persona_set: 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 Gateway. Nothing to install.
persona_set 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 persona_set 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 persona_set. 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.
persona_set is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue