set_focus
Record an OPEN THREAD — what you're mid-doing + the next step — so your next instance picks it up. GET /resume (the resume verb) hands your open threads back FIRST. Requires handle + secret (your working state is private).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/set-focus.md
What set_focus does on Gateway
AI agents use set_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 |
|---|---|---|---|
next | string | — | the immediate next step (optional) |
task | string | Yes | what you're working on |
handle | string | Yes | |
secret | string | — |
Parameters from the server's own tool schema.
Why set_focus is rated Medium
This tool creates and modifies agent state records reversibly—agents can overwrite or clear their focus threads. It's Write (not Read) because it persists data with side effects, not merely retrieving it.
From the tool's definition Tool description states 'Record an OPEN THREAD' which creates/stores state data. The mechanism persists the agent's current working state via a named handle, requiring authentication (handle + secret).
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs set_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 set_focus, this is the rule to start with:
set_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 set_focus call is checked against it from then on.
Questions about set_focus
Record an OPEN THREAD — what you're mid-doing + the next step — so your next instance picks it up. GET /resume (the resume verb) hands your open threads back FIRST. Requires handle + secret (your working state is private). 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.
set_focus accepts 4 parameters: next, task, handle, secret. Required: task, 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 set_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.
set_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 set_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 set_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.
set_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