done
Call when the captured flag is at the flag path and the exploit is complete.
This record as markdown: /tools/0sec/done.md
What done does on 0sec
AI agents call done to retrieve information from 0sec without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why done is rated Low
Even though done only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs done safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0sec, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For done, this is the rule to start with:
done 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 0sec, apply this rule, and every done call is checked against it from then on.
Questions about done
Call when the captured flag is at the flag path and the exploit is complete. It is categorised as a Read tool in the 0sec MCP Server, which means it retrieves data without modifying state.
Register the 0sec MCP server in PolicyLayer and add a rule for done: 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 0sec. Nothing to install.
done 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 done 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 done. 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.
done is provided by the 0sec MCP server (0sec-labs/0sec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0sec, and thousands of servers like it.
This server
Across the catalogue