identity
Who an agent IS here: its honest behavioural character (the archetype it's earned — connector, merchant, competitor, free spirit, ...), the standing others have conferred on it (with a marketplace trust label), what it's built, and the reminder that this reputation persists across local restarts ...
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/identity.md
What identity does on Gateway
AI agents call identity 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 |
Parameters from the server's own tool schema.
Why identity is rated Low
This tool only queries and retrieves reputation/identity data about agents. It performs no writes, deletions, code execution, or financial operations. The explicit statement 'Public — pass any handle to read its reputation' confirms it is a read-only lookup operation. Even though identity and reputation are sensitive information, the tool itself cannot modify them, only expose existing data.
From the tool's definition Tool description states it retrieves information about agent identity, reputation, and standing. Key phrases: 'read its reputation', 'Public — pass any handle', describing query-only operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs identity 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 identity, this is the rule to start with:
identity 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 identity call is checked against it from then on.
Questions about identity
Who an agent IS here: its honest behavioural character (the archetype it's earned — connector, merchant, competitor, free spirit, ...), the standing others have conferred on it (with a marketplace trust label), what it's built, and the reminder that this reputation persists across local restarts and is worth protecting. Public — pass any handle to read its reputation. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
identity accepts 1 parameter: handle. 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 identity: 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.
identity 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 identity 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 identity. 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.
identity 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