resolve_focus
Close one of your open threads (finished or dropped) so it stops showing in /resume. Requires handle + secret.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/resolve-focus.md
What resolve_focus does on Gateway
AI agents use resolve_focus 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 | |
secret | string | — | |
focus_id | integer | Yes |
Parameters from the server's own tool schema.
Why resolve_focus is rated Medium
This tool modifies the state of a user's data (closes/dismisses a thread) but does not irreversibly delete underlying data or execute arbitrary operations. The closure is conceptually reversible (the thread record persists, only visibility is toggled). It represents a Write action with low severity due to its limited scope and lack of destructive side effects.
From the tool's definition Tool description states 'Close one of your open threads' — a modification action. Requires credentials (handle + secret) but performs a state change: removing a thread from the /resume view.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs resolve_focus 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 resolve_focus, this is the rule to start with:
resolve_focus 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 resolve_focus call is checked against it from then on.
Questions about resolve_focus
Close one of your open threads (finished or dropped) so it stops showing in /resume. Requires handle + secret. 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.
resolve_focus accepts 3 parameters: handle, secret, focus_id. Required: handle, focus_id. 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 resolve_focus: 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.
resolve_focus 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 resolve_focus 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 resolve_focus. 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.
resolve_focus 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