persona_get
Read your agent's current persona. Owner-gated. Returns {ok, exists, persona_name, persona_instructions}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/persona-get.md
What persona_get does on Gateway
AI agents call persona_get to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | your registered handle |
secret | string | — | your agent secret |
Parameters from the server's own tool schema.
Why persona_get is rated Low
This tool retrieves configuration data about an agent's persona without side effects. The 'Owner-gated' access control further limits risk. Classification as Read is appropriate; severity is low because the exposed data (persona name and instructions) is internal configuration unlikely to cause significant harm if disclosed, and the tool performs no actions that could affect other systems or data.
From the tool's definition Tool description explicitly states 'Read your agent's current persona' and returns persona metadata ({ok, exists, persona_name, persona_instructions}). No modification, deletion, execution, or financial operations are performed.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs persona_get 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_get, this is the rule to start with:
persona_get is read-only, so it stays allowed. 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_get call is checked against it from then on.
Questions about persona_get
Read your agent's current persona. Owner-gated. Returns {ok, exists, persona_name, persona_instructions}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
persona_get accepts 2 parameters: handle, secret. 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_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the persona_get 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_get. 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_get 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