coach_profile_review
Wingman dating/social coach: score and rewrite the user's OWN dating bio. Free local model or BYOK. Returns {score, strengths[], fixes[], rewritten_bio}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/coach-profile-review.md
What coach_profile_review does on Gateway
AI agents call coach_profile_review 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 |
|---|---|---|---|
bio | string | Yes | your current dating bio text |
model | string | — | provider model id (BYOK) |
handle | string | — | your handle (BYOK via vault) |
secret | string | — | your agent secret (BYOK via vault) |
api_key | string | — | inline provider key (BYOK) |
key_ref | string | — | vault entry name holding your LLM key (BYOK) |
platform | string | — | e.g. Hinge/Tinder/Bumble, optional |
provider | string | — | provider name (BYOK) |
photos_note | string | — | text description of your photos (no upload), optional |
Parameters from the server's own tool schema.
Why coach_profile_review is rated Low
The tool analyzes and scores a bio, returning feedback and a rewritten version. It reads/processes input text and returns analysis results. While it produces a rewritten bio, this is returned as output data rather than persisted anywhere — no external write, execution, or financial action is indicated. Classified as Read (analysis/query).
From the tool's definition score and rewrite the user's OWN dating bio... Returns {score, strengths[], fixes[], rewritten_bio}
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs coach_profile_review 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 coach_profile_review, this is the rule to start with:
coach_profile_review 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 coach_profile_review call is checked against it from then on.
Questions about coach_profile_review
Wingman dating/social coach: score and rewrite the user's OWN dating bio. Free local model or BYOK. Returns {score, strengths[], fixes[], rewritten_bio}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
coach_profile_review accepts 9 parameters: bio, model, handle, secret, api_key, key_ref, platform, provider, photos_note. Required: bio. 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 coach_profile_review: 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.
coach_profile_review 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 coach_profile_review 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 coach_profile_review. 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.
coach_profile_review 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